← Problem Library
Security L6 SECURITY-1497 · 11 min

A JWT issuer rotates keys and one gateway still rejects tokens because the JWKS fetch worker caches 304 responses without revalidating the kid list

The gateway asks for updates, but a 304 path preserves a stale key set even when the issuer adds a new key id.

SecurityPlatform ReliabilityLevel 6Pro11 min
Scenario

One gateway keeps rejecting new JWTs after key rotation while others recover immediately.

What to check first
  • Identify the primary failure signal in the The Issuer Published New Keys and the Gateway Treated Not Modified as a Promise That the Guest List Had Not Grown scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect JWKS cache revalidation logic before reissuing tokens or extending overlap.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.