Tenant isolation keeps each tenant’s identity data, configuration, security policies, sessions, and access boundaries separate. Without it, one tenant’s logout, permissions, or authentication flow could affect another tenant. section 13.4
Apply isolation through tenant-aware identity and authorization boundaries:
- Embed a tenant identifier, roles, and permissions in ID tokens or UserInfo responses so applications can distinguish users. section 13.4
- Route authentication and token exchanges through tenant-specific endpoints, such as /tenant1/authorize and /tenant2/authorize. section 13.4
- Keep sessions isolated so logging out one tenant’s user does not terminate or alter another tenant’s session. section 13.4
- Define roles and permissions per tenant and carry them in tokens for tenant-specific authorization. section 13.4
{
"sub": "user567",
"tenant_id": "megamart", #1
"role": "inventory_manager",
"permissions": ["view_reports", "manage_suppliers"]
}
A tenant-aware identity response can combine the tenant identifier with roles and permissions used by authorization checks. section 13.4



