Skip to content

OAuth2 provider does not use the CrendentialProvider to get/set the token #1127

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
Open
Tracked by #1893
gabriel-farache opened this issue Apr 30, 2025 · 0 comments · May be fixed by #1126
Open
Tracked by #1893

OAuth2 provider does not use the CrendentialProvider to get/set the token #1127

gabriel-farache opened this issue Apr 30, 2025 · 0 comments · May be fixed by #1126

Comments

@gabriel-farache
Copy link
Contributor

Since #1104 was introduced, all providers must use the CrendentialProvider instance to get/set the token instead of doing it internally.

The OAuth2 provider does not do that and keep doing it internally which introduce an behaviour exception and may limit the scope of the usage for CrendentialProvider
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #1127 - Use CredentialProvider in OAuth2 provider gabriel-farache/quarkus-openapi-generator
1 participant
@gabriel-farache