-
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
"password" and "application" flows are broken #3128
Comments
Any progress on this? |
@Naid405 I will provide you with more info asap |
@Naid405 'application' flow is fixed, 'password' flow type 'body-parameter' changed. Fixes are in master |
Thank you, @bodnia. |
I think I can make it a default one. I'll notify you here once it's merged |
#3128 make request-body type default for aouth2 password flow
@Naid405 merged to master |
Thanks again! |
Hi, @bodnia. There's another bug with this now - if you just open the "Authorize" window, type username and password and hit the button it doesn't send the client credentials. Only after I select other type and select "Request Body" back it start sending client credentials. |
@Naid405 can you please file a separate issue for that? |
Here is my thorough summary of the state of OAuth2 Password Flow implementation in Swagger-UI: #3227. |
When reporting an issue, please provide the following details:
According to spec at https://tools.ietf.org/html/rfc6749:
For "password" flow "username" and "password" should be passed in the body using the "application/x-www-form-urlencoded" and "client_id" and "client_password" should be passed via basic auth.
For "application" flow "client_id" and "client_password" should just be passed via basic auth.
Currently none of the options available for "password" flow provide the ability to authorize the way specification suggests since they don't actually send client credentials the way specification suggests.
Also maybe specification way should be the default one.
The text was updated successfully, but these errors were encountered: