Zero-Downtime Rotation
Zero-downtime rotation changes signing keys while active tokens remain valid. The pattern: generate a new key with a new kid, sign new tokens with it, keep the old key in the verifier key store until all tokens signed with it expire, then remove the old key. JWKS endpoints may publish multiple keys simultaneously. This avoids mass session termination during planned rotation. Implementations across Node.js, Python, Go, Ruby, and Java follow the same RFC standards, so concepts transfer directly between stacks. Security reviews should treat this as part of your full authentication threat model, not an isolated configuration detail. Document expected behavior for client teams so tokens are issued, stored, and validated consistently across services.
Why It Matters
Every production JWT system should implement this before the first rotation event. Without overlap, users face sudden logout when ops updates a single global secret. Automate kid lifecycle and monitor tokens still referencing retired kids. Getting this wrong often surfaces only after an incident, when forged or replayed tokens expose gaps in validation or secret handling. Platform teams should encode these rules in libraries, linting, and deployment checklists so individual services cannot drift silently. Pair technical controls with monitoring: log verification failures, track unusual token lifetimes, and alert on spikes in 401 responses. Review this during every auth-related change, including framework upgrades, CDN additions, and new mobile or third-party clients.
Related Terms
Related Tools
Related Articles
Frequently Asked Questions
How long should overlap last?
At least your longest access token lifetime, often longer if refresh tokens are JWTs signed with the same key. Consult your JWT library documentation for exact option names, defaults, and error types. When in doubt, prefer stricter validation and shorter token lifetimes over permissive shortcuts.
What if I skip overlap?
All existing tokens fail verification immediately — acceptable only in emergency revocation. Consult your JWT library documentation for exact option names, defaults, and error types. When in doubt, prefer stricter validation and shorter token lifetimes over permissive shortcuts. Test edge cases with expired, malformed, and wrong-algorithm tokens in CI before shipping auth changes.
Does zero-downtime apply to HS256?
Yes. Verifiers hold multiple symmetric secrets keyed by kid during the transition. Consult your JWT library documentation for exact option names, defaults, and error types. When in doubt, prefer stricter validation and shorter token lifetimes over permissive shortcuts. Test edge cases with expired, malformed, and wrong-algorithm tokens in CI before shipping auth changes.