-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Basic auth shouldn't require a password change reverted? #5410
Comments
I think all that needs to be done is to remove the required flag here:
|
I agree. We found that removing this attribute manually via the browser inspector fixes the issue so we wrote a Swagger plugin as a temporary workaround until this is fixed. (There is almost certainly a more idiomatic way to do this in React, but it's not a framework I'm familiar with.)
|
Hi, |
PR is welcome to remove the required attribute 😄 |
Just ran into this issue and since a solution was proposed but no PR yet, here is one: #5812 |
I am using swagger-ui version 3.19.5 (via Swashbuckle.AspNetCore.SwaggerUI v4.0.1) with an API that uses basic auth with a username but no password.
(One example of a high traffic and well-designed API that uses this approach for authentication is the Stripe API.)
It looks like in #2114 swagger-ui was changed to not require a password, but in the authorize dialog the password seems to always be required.
Was reverting this change intentional? Is there a workaround I can use to make it optional?
The text was updated successfully, but these errors were encountered: