liveBook · Manning

Openid connect

As explained in Authorization in Action

OpenID Connect is an identity layer built on OAuth 2.0 that enables clients to verify user identity and obtain basic profile information from an authorization server.

When someone uses a Google, Facebook, or Apple account to sign in to another application, OpenID Connect helps federate that identity across services. section 2.2.2

OpenID Connect (OIDC) is an authentication and authorization framework that propagates identity attributes in signed tokens. It helps applications and identity providers share consistent identity information across organizational systems. section 3.3.2 section 2.2.2

OpenID Connect contributes to interoperability in two closely related ways:

  • Federates identity providers so users can access multiple applications without separate application-specific identities. section 2.2.2
  • Propagates identity attributes in signed tokens, helping authentication and authorization decisions use synchronized account information. section 3.3.2

How Authorization in Action covers it

How deep it goes
Defines federation and signed-token propagation, but stops short of solving the broader identity interoperability problem.
Examples
Uses Google, Facebook, and Apple sign-in as recognizable federated-login examples.
What you can do after
Evaluate identity propagation across systems and distinguish federation from provisioning and directory protocols.
How it connects
Connects authentication, authorization, identity providers, signed tokens, SCIM, LDAP, and SAML.

Also explained in

Compare how 13 books explain openid connect →

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.