fix(auth): use eventual consistency for hosted refresh-token blob
Strong consistency is unavailable in Netlify's Lambda compatibility mode (serverless-http + connectLambda): the runtime never supplies the `uncachedEdgeURL` strong reads require, so the read at the start of issueRefreshToken threw BlobsConsistencyError and aborted every refresh-cookie write (Set-Cookie never sent; Cookies tab always empty).
Switch the gateway-auth store to eventual consistency (same model the billing store already uses successfully on this site). Rotation, reuse detection, and family revocation are unchanged; the residual exposure is the documented <=60s edge-propagation window. Primary defenses intact: 256-bit opaque token, HttpOnly cookie, whole-map last-write-wins, family burn on detected reuse. Hardening path (canister / API origin) documented.
Tests updated to assert eventual (and reject strong) consistency; 24/24 pass.
0 comments
muse hub commit comment sha256:64a8cc8e0690ce9ab408e31780da78a7596245b56543a92fe8a77a1459ac766a --body "your comment"
No comments yet. Be the first to start the discussion.