Skip to content
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

oAuth2, send client secret and id using POST parameters for application flow (client credentials) #3217

Closed
jakubzloczewski opened this issue Jun 9, 2017 · 2 comments

Comments

@jakubzloczewski
Copy link

jakubzloczewski commented Jun 9, 2017

  • swagger-ui version : 3.0.13

Some oAuth2 clients are registred with option token_endpoint_auth_method = client_secret_post. That means when they are trying to get token using /token endpoint they have to provide client_secret and client_id using request body instead of Authorization header.
Current implementation supporting only clients registered with option token_endpoint_auth_method = client_secret_basic.

More about this here: https://tools.ietf.org/html/rfc7591#section-2

It would be nice to have way to control which method will swagger-ui use to get token. As nothing was mentioned in OpenAPI spec maybe we can just add dropdown so user can pick desired method.

@frol
Copy link

frol commented Jun 10, 2017

Here is my thorough summary of the state of OAuth2 Password Flow implementation in Swagger-UI: #3227.

@webron
Copy link
Contributor

webron commented Jul 5, 2018

Closing in favor of #3227, as part of reorganizing the tickets. Thanks for the feedback.

@webron webron closed this as completed Jul 5, 2018
@lock lock bot locked and limited conversation to collaborators Jul 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants