← Problem Library
Security L7 SECURITY-009 · 29 min

Mutual TLS works on primary path but fails after east-west failover

Certificates and policies look valid, but the fallback service path presents a different trust context and breaks authentication.

SecurityTLSPlatform ReliabilityLevel 7Pro29 min
Scenario

Certificates and policies look valid, but the fallback service path presents a different trust context and breaks authentication.

What to check first
  • Identify the primary failure signal in the TLS 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
Why do mTLS issues show up after failover but not on the primary path?

Secondary paths often have a different certificate bundle, trust store, or proxy hop than the primary service route.