← Problem Library
Security L7 SECURITY-066 · 20 min

JWKS cache on the API gateway stays stale after OIDC signing key rotation

The identity provider is healthy and publishes the new key, but valid tokens still fail because the gateway never refreshed its cached trust material in time.

SecurityFoundation OpsLevel 7Free20 min
Scenario

The identity provider is healthy and publishes the new key, but valid tokens still fail because the gateway never refreshed its cached trust material in time.

What to check first
  • Identify the primary failure signal in the Key Rotation Cache Drift 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

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.