liveBook · Manning

Tenant-specific endpoint

As explained in Software Security for Developers

A tenant-specific endpoint is an identity-service endpoint whose routing and authentication context are associated with one tenant.

A tenant-specific endpoint routes authentication requests and token exchanges through an endpoint associated with one tenant. Separating these routes helps keep tenant sessions and authentication flows isolated. section 13.4

Separate authorization routes

A multitenant application can direct Tenant 1 to https://idp.example.com/tenant1/authorize and Tenant 2 to https://idp.example.com/tenant2/authorize. Each tenant therefore uses its own authorization route instead of sharing one endpoint. section 13.4

{
  "sub": "user567",
  "tenant_id": "megamart",   #1
  "role": "inventory_manager",
  "permissions": ["view_reports", "manage_suppliers"]
}

Tenant-aware claims can complement endpoint separation by identifying the tenant and permissions in returned identity data. section 13.4

How Software Security for Developers covers it

How deep it goes
Defines endpoint separation and illustrates two authorization URLs without detailing implementation internals.
Examples
Uses tenant1 and tenant2 authorization URLs plus a tenant-aware identity payload containing tenant_id, role, and permissions.
What you can do after
Apply it via OpenID Connect by routing each tenant’s authentication flow to its corresponding authorization endpoint.
How it connects
Connects tenant isolation with OpenID Connect, dynamic client registration, tenant-aware claims, and role-based access control.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Security for Developers. The section links point to the parts of the book it draws on.