← Problem Library
Security L6 SECURITY-1469 · 12 min

A JWKS rotation succeeds and one edge cache still serves the old key set because the purge missed a content-negotiated variant family

The new keys are published, but one cache branch was not evicted with the rest.

SecurityPlatform ReliabilityLevel 6Pro12 min
Scenario

Some clients validate new JWTs while one region keeps seeing the old JWKS after rotation.

What to check first
  • Identify the primary failure signal in the The New Keys Reached the Edge and One Cache Family Never Received the Eviction Notice 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

Compare purge scope and cache variants before reissuing tokens.

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.