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

Support pkce with oauth2 #131

Closed
jgramoll opened this issue May 6, 2022 · 1 comment · Fixed by #134
Closed

Support pkce with oauth2 #131

jgramoll opened this issue May 6, 2022 · 1 comment · Fixed by #134
Assignees
Labels
enhancement New feature or request

Comments

@jgramoll
Copy link
Contributor

jgramoll commented May 6, 2022

I am trying to use utoipa-swagger-ui with oauth2 (https://github.com/swagger-api/swagger-ui/blob/master/docs/usage/oauth2.md). I need to be able to set the usePkceWithAuthorizationCodeGrant flag so that I can authorize with pkce. Is there currently a way to support this or something that could be added?

@juhaku
Copy link
Owner

juhaku commented May 6, 2022

Yeah, unfortunately the configuration options via utoipa-swagger-ui is far limited at the moment. Currently there is no way to configure other than the url(s) for the api docs.

Support for this could be added and is pretty straight forward to implement. I've had a plans to improve the Swagger UI configuration options but hadn't had time to work on this. I'll add a task to the project's kanban board about this so that it will be done some point in future. Currently there are already quite a few things to work on.

@juhaku juhaku added the enhancement New feature or request label May 9, 2022
@juhaku juhaku linked a pull request May 9, 2022 that will close this issue
@juhaku juhaku moved this to Done in utoipa kanban May 10, 2022
@juhaku juhaku moved this from Done to Released in utoipa kanban Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Released
Development

Successfully merging a pull request may close this issue.

2 participants