You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
exalate-issue-syncbot
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-syncbot
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
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
The text was updated successfully, but these errors were encountered: