docs: note disabled-account access_denied outcomes during auth flow
Clarify that account status changes (disabled) may surface as access_denied during provider login/authorization, and integrations should handle these outcomes explicitly.
This commit is contained in:
@@ -136,6 +136,7 @@ try {
|
|||||||
|
|
||||||
`UserInfoException` with `invalid_token` can occur when provider-side subject scope is no longer active (for example user/project disabled) between token issuance and userinfo retrieval.
|
`UserInfoException` with `invalid_token` can occur when provider-side subject scope is no longer active (for example user/project disabled) between token issuance and userinfo retrieval.
|
||||||
`TokenExchangeException` with `invalid_grant` can also occur when provider-side client/user/project state is inactive at exchange time.
|
`TokenExchangeException` with `invalid_grant` can also occur when provider-side client/user/project state is inactive at exchange time.
|
||||||
|
Provider login/authorization steps can also fail with `access_denied` when account status is disabled before completion.
|
||||||
|
|
||||||
## Operational guidance
|
## Operational guidance
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user