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
Commit c5f2e1f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(credentials): pace throttled and Vanta token retries and replay remembered failures without the lock
- A 429 that names no Retry-After is replayed for at least a minute, doubling
up to the five-minute cap, instead of the 5 s outage curve.
- The outage backoff never undercuts Entra's 5 s first-retry floor through jitter.
- Vanta asks for a token at most once per 15 s while exchanges fail (no
in-request retry, replay floored), within its documented 5 tokens a minute,
through a new optional minExchangeIntervalMs on the coordinated resolver.
- A remembered failure and the still-valid fallback are served from committed
rows before the application lock is taken, so a refresh outage no longer
serializes every resolution behind the lock.
- retryAfterMs now only carries a provider's Retry-After; a replayed memo
reports its remainder as the additive replayForMs, which the per-instance
layer honors exactly.
- One decode/verify path for stored tokens; the stored-failure permanence
check uses isPermanentTokenFailureCode instead of building an error.
0 commit comments