fix
patch
auth
feat/phase-2g-bundle
#56 / 100
fix(auth): surface refresh-cookie write failures instead of swallowing them
The hosted gateway's issueRefreshCookieSafe caught and discarded every error from the refresh-token store write, so a persistent-login failure (no HttpOnly cookie set at login) produced no signal in the logs at all. Log issuance success and, on failure, the error plus authBlobPresent — which distinguishes a non-provisioned strong-consistency auth blob (silent fallback to a file write that fails on the read-only function filesystem) from a rejected blob write. Add a wiring test asserting the failure is logged, not silently swallowed.
sha256:294c8db237ca1a8e9282b4b61df29b44e6e5b5a701245e3be932e5ae8add4a8d
sha
sha256:362badaccac9ea368af7b6c9a47f6d0fc4421750bfe203772c05447c7bb36060
snapshot
Older
Merge pull request #219 from aaronrene/feat/persistent-login
sha256:8ae6bfe799cfa5d775310caa5310444ff6cb5b0d6cd7e6b0353af45de7de5851
All commits
Newer
Merge pull request #220 from aaronrene/fix/refresh-cookie-logging
sha256:4df4a8a23a8ed97955e12117da5a9027ed0b45cd82264498148e1bd0784e72f4
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:294c8db237ca1a8e9282b4b61df29b44e6e5b5a701245e3be932e5ae8add4a8d --body "your comment"
No comments yet. Be the first to start the discussion.