← Problem Library
Security L5 SECURITY-1484 · 10 min

A Cloudflare Access app validates JWTs and one service still denies users because the audience changed when the app slug was renamed

Tokens are valid, but one backend keeps checking the old audience value after an app rename.

SecurityPlatform ReliabilityLevel 5Pro10 min
Scenario

Access works at the edge and one backend still rejects requests after an Access application rename.

What to check first
  • Identify the primary failure signal in the The Token Was Good and the Service Kept Asking for the Name the Gate Used Before It Was Repainted 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 backend audience checks with current app identifiers before rotating keys.

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.