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.

Sign up for GitHub

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

Jump to bottom

Fix Swagger to use OAuth 2.0 Implicit flow when authenticating using Keycloak #23

Open
benjaminkostiuk opened this issue Aug 25, 2021 · 0 comments
Open

Fix Swagger to use OAuth 2.0 Implicit flow when authenticating using Keycloak #23

benjaminkostiuk opened this issue Aug 25, 2021 · 0 comments
Labels
bug Something isn't working priority:medium Medium priority work item
Projects
Puff Platform

Comments

@benjaminkostiuk
Copy link
Member

Don't want to have dev deployed and exposing the client secret for the user-auth client. Swagger should use the implicit oauth flow instead of client credentials, taking advantage of the keycloak login page.
@benjaminkostiuk benjaminkostiuk added this to To do in Puff Platform via automation Aug 25, 2021
@benjaminkostiuk benjaminkostiuk added bug Something isn't working priority:medium Medium priority work item labels Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working priority:medium Medium priority work item
Projects
Puff Platform
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@benjaminkostiuk