liveBook · Manning

Identity provider

As explained in Authorization in Action

A central identity provider is a service that centrally manages digital identities and supplies authentication or identity information to relying applications or other systems.

An identity provider (IdP) centrally manages accounts, authenticates users, and supplies identity attributes to relying parties (RPs). In an enterprise example, an employer authenticates an employee for a benefits provider, returning only the attributes agreed between the organizations. section 2.5.2

The IdP–RP exchange uses a federation protocol such as Security Assertion Markup Language (SAML), OAuth, or OpenID Connect. Trust frameworks—formal agreements or click-through terms—define how identity data may be used and what guarantees the IdP provides. section 2.5.2

Identity in a multi-tenant platform

A multi-tenant collaboration platform must obtain identity from outside its own system and keep tenancy as a distinct, enforceable boundary. Supporting tenant-controlled identity providers prevents the platform from making every tenant a subject of its internal identity system. section 13.3

How Authorization in Action covers it

How deep it goes
Explains accounts, authentication, attributes, protocols, and trust agreements, but defers protocol implementation details.
Examples
Uses employer-to-benefits-provider federation, Google account sign-up, and tenant-controlled identity for a collaboration platform.
What you can do after
Evaluate federated architectures by separating identity ownership, application reliance, protocol exchange, and data-sharing governance.
How it connects
Connects federated identity with relying parties, SAML, OAuth, OpenID Connect, trust frameworks, and multi-tenancy.

Also explained in

Compare how 12 books explain identity provider →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Authorization in Action. The section links point to the parts of the book it draws on.