← Problem Library
Security L6 SECURITY-1452 · 12 min

A Vault Transit key rotates and one app tier still rejects JWE tokens because its allowlist pins the old key version in the kid parser

Rotation succeeds, but one client parser only trusts the previous kid pattern and refuses the new encrypted payloads.

SecurityPlatform ReliabilityLevel 6Pro12 min
Scenario

Encrypted tokens fail only in one app tier after Transit key rotation while decryption still works elsewhere.

What to check first
  • Identify the primary failure signal in the The Key Rotated Cleanly and the Client Kept Looking for Yesterday's kid Shape 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 client-side kid allowlists before rolling the key again.

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.