← Problem Library
Security L7 SECURITY-1371 · 15 min

A Grafana SSO login succeeds and users land as Viewers because the team claim moved into a nested groups object that the old role mapping expression never traverses

Authentication works, yet authorization degrades because the mapper still looks at the previous flat claim location.

SecurityIAMPlatform ReliabilityLevel 7Pro15 min
Scenario

An IdP claim cleanup lands and later every Grafana login works but the expected team roles stop being assigned.

What to check first
  • Identify the primary failure signal in the IAM 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 the exact IdP payload before editing Grafana org settings or manually assigning roles.

Questions worth viewing together
What should you verify first when A Grafana SSO login succeeds and users land as Viewers appears?

Community-field security problem inspired by Grafana community cases where nested group claim changes broke role mapping. SSO authorization failures often come from claim shape drift, not from authentication or token issuance failures.

What usually causes A Grafana SSO login succeeds and users land as Viewers in production?

Teams often blame Grafana org sync when the role mapping expression is still reading the old claim path.

What should you document after resolving A Grafana SSO login succeeds and users land as Viewers?

Role mapping expressions should be regression-tested whenever IdP teams or groups claims are restructured.