GeezerVison

Sign-out now sends the OIDC refresh token to the identity provider's
revocation endpoint before it clears the local session, so the provider
stops issuing access tokens for that session. Only the refresh token is
revoked, because AWS Cognito's revocation endpoint rejects access
tokens. If revocation fails, the client logs a warning and sign-out
still completes.

The authentication docs say that token revocation must be enabled for
the app client, and that access tokens already issued stay valid until
they expire, because pipeline-manager validates them locally.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

Sign-out waits for the identity provider to revoke the refresh token.
The OIDC client aborts each revocation attempt after 10 s and retries an
aborted attempt twice, with no option to change this, so a provider that
does not answer delayed sign-out by about 30 s.

The console now wraps the client's fetch so that an aborted revocation
request fails with a TimeoutError, which the client does not retry.
Sign-out then waits at most 10 s and completes with the refresh token
unrevoked, as it does for any other revocation failure.

The Sign Out button shows a pending state and ignores clicks while
sign-out waits.

Tests cover a provider that does not answer, a sign-out with the logout
extras the console passes for Cognito, and the pending button.

The dummy OIDC provider publishes a revocation endpoint and forgets a
refresh token when the client revokes it. A new e2e test signs in through
the provider, signs out, and checks that the console revoked the refresh
token and that the provider rejects it afterwards. This covers the
generic OIDC path, where the console finds the revocation endpoint
through discovery.

The signed-in profile button gets the same accessible name as the
signed-out one, so the test can open the menu.

The client logs nothing when the provider answers a revocation with an
error status. The code comment no longer claims that a failed revocation
is logged, and the docs say that the console logs no error when
revocation is disabled.