← Problem Library
Security L6 SECURITY-1351 · 14 min

A Grafana login succeeds and team access disappears because the IdP moved membership claims under groups while the role mapping still reads the old flat team claim

Authentication is healthy, yet dashboards and folders look empty because the RBAC mapper still expects the pre-migration claim shape.

SecurityPlatform ReliabilityLevel 6Pro14 min
Scenario

An SSO schema update lands and later Grafana users can log in but lose the permissions tied to their old team claim mapping.

What to check first
  • Identify the primary failure signal in the The User Arrived With Valid Claims in a Shape the Mapper No Longer Recognized 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 live token claim structure before recreating teams or reassigning dashboards manually.

Questions worth viewing together
What should you verify first when A Grafana login succeeds and team access disappears appears?

Community-field security problem inspired by Grafana community patterns where role mapping broke after team claims moved into a different OIDC attribute. Authorization failures after IdP updates often come from claim-shape drift, not from broken login.

What usually causes A Grafana login succeeds and team access disappears in production?

Teams often blame stale sync jobs when the mapper is just reading the wrong claim path.

What should you document after resolving A Grafana login succeeds and team access disappears?

Every IdP schema change should trigger a downstream role-mapping review for OIDC-backed apps.