liveBook · Manning

Identity provider

As explained in Fundamentals of Cybersecurity

An identity provider is a service that authenticates identities, enforces access policies, and issues trusted assertions or tokens to applications.

An identity provider (IdP) is a service that creates and manages digital identities, authenticates people, and gives applications trusted identity information. It often sits between a directory service and the applications employees use, so those applications do not need to contact the directory directly. The IdP can also enforce policies such as multi-factor authentication and conditional access. section 10.3 section 10.3.1

A typical sign-in works like this:

  • The employee authenticates with the IdP, often using multi-factor authentication. section 10.3.2
  • The IdP issues a security token containing identity information or claims. An application validates the token rather than asking for another sign-in. section 10.3 section 10.3.2
  • The application applies its own authorization rules. A valid token establishes who signed in; it does not, by itself, decide everything that person may do. section 10.3.2

One sign-in, several applications

An employee signs in once, then opens email, a ticketing system, and an internal wiki without reentering credentials. Think of the IdP as a theme park entrance that checks identification and issues a wristband. Each ride checks the wristband, but can still apply its own entry rules. If the wristband is lost, the entrance can invalidate it; similarly, an IdP can revoke a token or end a session. section 10.3.2

An IdP can also support federated identity management: one domain’s identity system vouches for a user to another. For example, an employee in an EU domain can access U.S. resources without creating new credentials. The receiving application validates the signed token and still applies its own access rules. section 10.3.3

How Fundamentals of Cybersecurity covers it

How deep it goes
Traces token-based single sign-on and federation flows, stopping short of protocol configuration steps.
Examples
Uses an employee accessing several applications, a theme park wristband, and cross-domain access between EU and U.S. resources.
What it assumes
Defines identity management and explains relying parties through an analogy before naming token standards.
What you can do after
Evaluate/understand where an IdP sits between directories and applications, and distinguish authentication from application authorization.
How it connects
Links directory services, multi-factor authentication, single sign-on, federated identity management, and application authorization.

Also explained in

Compare how 14 books explain identity provider →

Related concepts

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