Skip to content

auth: a refused bearer expires the edge session so re-sign-in is real (0.1.9) - #7

Merged
reoring merged 1 commit into
mainfrom
reauth-on-401
Nov 10, 2026
Merged

reoring merged 1 commit into
mainfrom
reauth-on-401

Conversation

@reoring

@reoring reoring commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

On a 401 the SPA navigates to / to re-run sign-in, but the edge only checks its own HMAC/expiry cookies and replays the token the server refused, so the second request fails too and the user sees the access-denied screen even after signing in again.

The 401 response now expires the edge OIDC cookies for this host (IdToken/AccessToken/RefreshToken/OauthHMAC/OauthExpires and sign-in state). The next navigation goes through the IdP and mints a new token from the still valid SSO session. No logout: the SSO session and other apps are untouched. The existing 60 s guard still stops a loop when the new token is refused as well. The rejection log line gains edge_cookies_expired=<n>.

Not verified live: that the edge forwards its cookies upstream (n > 0); the log line will show it on the first occurrence.

@reoring
reoring merged commit 458fb7b into main Nov 10, 2026
3 checks passed
@reoring
reoring deleted the reauth-on-401 branch November 10, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant