← Problem Library
Security L6 SECURITY-1461 · 12 min

A Vault Agent rotates the certificate and one JVM still presents the old chain because its alias map keeps the old file target cached

The new cert is present on disk, but the running process still serves the previous alias binding.

SecurityPlatform ReliabilityLevel 6Pro12 min
Scenario

An mTLS client keeps presenting the retired chain after Vault Agent rotates the file-backed certificate.

What to check first
  • Identify the primary failure signal in the The Certificate Changed on Disk and the Alias Map Kept Handing Out Yesterday's Chain 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 alias-cache invalidation before rotating certificates 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.