fix(bd-3o8zmz46): evidence-based session expiry handling in hub-client#268
Merged
Conversation
/auth/me now reports the token's exp and the client schedules refresh from it (removing the refocus drift bug); a new useAuthProbe polls /auth/me while sync is disconnected (two-strike 401 escalation); network errors never log the user out; the login screen says when the session expired.
ec38d81 to
5b14edd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the Google ID token expired and One Tap renewal was unavailable, the hub 401'd every Automerge WS upgrade while the SPA stayed "logged in" showing a permanent "working offline" banner (bd-3o8zmz46).
/auth/menow reports the token'sexpso the client schedules refresh from the real expiry (removing the refocus drift bug)useAuthProbepolls/auth/mewhile sync is disconnected and escalates on two consecutive 401s (renewal first, then an explicit "session expired" login screen)