docs: note JWT revocation-aware userinfo behavior

Update integration guidance that revoked JWT access tokens are now rejected on provider userinfo before natural expiry.
2026-02-26 13:00:51 +00:00
parent bbcada1317
commit 8bb3c1ce12
2 changed files with 2 additions and 0 deletions
@@ -131,6 +131,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`.
 - Handle provider callback errors (`error`, `error_description`) explicitly; treat `access_denied` as an expected user/authorisation outcome rather than a transport failure.
 - Expect `access_denied` even after the consent page is displayed if provider-side project membership or tenant scope changes before consent submission.
 - Expect provider token introspection to return `active=false` when user/project/client state is no longer active.
+- Expect revoked JWT access tokens to be rejected by provider `userinfo` even before token expiry.
 - Register only HTTPS redirect URIs in provider client settings (HTTP should be used only for localhost loopback during development).
 - Use OAuth/portal authentication endpoints for end users; provider admin login endpoints enforce separate admin scope checks.
 - For provider admin enrollment URL export operations, use `POST` with CSRF protection; do not automate them via unauthenticated `GET` links.