How to Rotate a Leaked JWT Secret Without Logging Users Out

Why mass logout is the wrong response

When a JWT secret leaks, the instinct is to rotate it immediately and invalidate every existing token - forcing every logged-in user to re-authenticate. That's a self-inflicted incident: support tickets spike, mobile users on flaky connections get bounced, and automated clients break.

The better approach is a rotation window. Issue all new tokens with NEW_SECRET, but accept both secrets during verification until the last OLD_SECRET-signed token has naturally expired (one token-lifetime from the moment you rotate). After that window, retire the old secret.

The dual-validate pattern in Python

Using pyjwt, try the new secret first. If the signature check fails, fall back to the old secret. Any other JWT error (expired, malformed) returns None immediately without trying the fallback.

import jwt

OLD_SECRET = "the-old-leaked-key"
NEW_SECRET = "the-new-rotated-key"


def issue_token(sub: str) -> str:
    # All new tokens use the new secret
    return jwt.encode({"sub": sub}, NEW_SECRET, algorithm="HS256")


def verify_jwt(token: str):
    for key in (NEW_SECRET, OLD_SECRET):
        try:
            return jwt.decode(token, key, algorithms=["HS256"])
        except jwt.InvalidSignatureError:
            continue          # wrong key - try the next one
        except jwt.PyJWTError:
            return None       # expired, malformed, etc - stop immediately
    return None

The order matters: try NEW_SECRET first so recently issued tokens never incur the overhead of a failing signature check against the old key.

What the rotation window looks like

Set NEW_SECRET in your environment or secrets manager before deploying the code change. That way the new signing key is ready the moment the first issue_token() call fires.

After the window closes

Once token_lifetime has elapsed since rotation, remove the OLD_SECRET fallback entirely:

def verify_jwt(token: str):
    try:
        return jwt.decode(token, NEW_SECRET, algorithms=["HS256"])
    except jwt.PyJWTError:
        return None

Keeping the fallback around indefinitely means a compromised token signed by the leaked secret stays valid forever - which defeats the rotation.

The production upgrade path

Symmetric secrets (HS256) share one key for signing and verification, which is why a leak forces a rotation window. Asymmetric algorithms (RS256, ES256) solve this structurally: the private key signs, the public key verifies. Rotating means publishing a new JWKS endpoint - no code change, no window needed. Auth0, Okta, and Cognito all expose this pattern out of the box.