I'm trying to get swagger-ui to talk to an already existing service. I can't get auth to work correctly, however.
I have an endpoint that accepts JSON and requires Basic Auth. I constructed my yaml file, authenticate via the UI, and swagger-ui generates a working curl example. But the Try it button doesn't work. On the server side, I see two OPTIONS requests that are both denied because of auth (401.) There are two things that I'm wondering could be involved. First, is it still necessary to add auth headers manually in JS for the button to work? I see some older github issues/list posts discussing that but I can't figure out if that is still correct. Second, is it something about CORS? I only vaguely know about it. I have this running all on the same host, but since they aren't actually using localhost would that mean there's a CORS issue? (Client browser is on another machine because the host is headless.) The server side is a webapp using Tornado. I'm not a core maintainer, so I'm not sure how it is/could be configured for CORS. For my test, I'm using an existing incoming webhook so there's something simple for swagger-ui to talk to. Is this something that should work? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
