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 introspection and userinfo should send a 503 when technical exception instead of 401 #9390

Closed
exalate-issue-sync bot opened this issue Nov 21, 2023 · 1 comment

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Nov 21, 2023

Currently, when a technical issue occurs during the introspection mechanism (used in gravitee-policy-oauth2) and in the userinfo mechanism (used in gravitee-policy-openid-connect-userinfo), these policies sends a 401 error.
It should be considered as a 503 error.

The fix need to be done in the OAuth2Provider resources so the good information is sent to policies

@exalate-issue-sync exalate-issue-sync bot changed the title PRODUCTION - An error occurs while checking OAuth2 token OAuth2 introspection should send a 503 when technical exception instead of 401 Nov 22, 2023
@exalate-issue-sync exalate-issue-sync bot changed the title OAuth2 introspection should send a 503 when technical exception instead of 401 OAuth2 introspection and userinfo should send a 503 when technical exception instead of 401 Nov 22, 2023
Copy link
Author

This issue will be fixed in versions 4.0.13, 3.20.24, 4.2.0, 4.1.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants