You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Improve reactive authentication algorithm in preparation for token caching #28
While replacing the older cache/refresh stack (#11/#12) with configurable caches built on current main, I found distinct OAuth behavior in #12 that is not part of the replacement cache work: a bounded use_dpop_nonce retry at the token endpoint, and explicit consent handling for the interactive offline_access authorization attempt. These deserve fresh review on the current component architecture; closing the superseded session stack should not lose those requirements. Existing token expiry handling (including absent expires_in) also remains unchanged by the cache adapter work.
#14's rejected-token retry and #23's logout/supersession fence remain open for their separate semantics. Storage-wide credential contexts and corresponding locks are tracked as issue-only work in #46. The generic cache/persistence scope is #45.
Activity
jeswr commentedon Sep 24, 2026
While replacing the older cache/refresh stack (#11/#12) with configurable caches built on current
main, I found distinct OAuth behavior in #12 that is not part of the replacement cache work: a boundeduse_dpop_nonceretry at the token endpoint, and explicit consent handling for the interactiveoffline_accessauthorization attempt. These deserve fresh review on the current component architecture; closing the superseded session stack should not lose those requirements. Existing token expiry handling (including absentexpires_in) also remains unchanged by the cache adapter work.#14's rejected-token retry and #23's logout/supersession fence remain open for their separate semantics. Storage-wide credential contexts and corresponding locks are tracked as issue-only work in #46. The generic cache/persistence scope is #45.