-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Never prompted for authentication #3774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It's unclear at what point the basic auth is set up for - is it to load the UI? the API definition? executing a call? |
The current version of Swagger-UI doesn't support authentication at all for 3.0.0 call executions. You can see that it's in our #3641 ticket. This feature is slated to be implemented and pushed by the end of the week. |
Apologies for the redundant ticket. Thank you |
No worries. It's better to get too many reports than no reports at all. Can never know when we might miss something. I'll be closing the ticket for now, but keep an eye out for this week's release! |
I am currently set up for basic auth. When I test any of the endpoints, I get a 401 and am never prompted for credentials. If I run Chrome with --disable-web-security, I am prompted as expected.
This also holds true for Firefox
I originally noticed this problem, but attributed it to CORS, but I think I have that issue resolve (no errors) but the authentication issue still persists
Spec
https://gist.github.com/masterof0/46dd46da6415e7f8ffd36c3de22fdc64
The text was updated successfully, but these errors were encountered: