Protocols
Saved & recent

OpenID Connect

Also called: OIDC

OpenID Connect adds an identity layer to OAuth 2.0. It lets a client learn about an end user authenticated by an OpenID Provider through an ID token and defined validation rules. This supports interoperable sign-in while OAuth access tokens remain concerned with access to resources.

For example, an application can sign a person in using an employer’s identity provider. It checks the ID token’s issuer, audience, expiry, and applicable cryptographic and nonce requirements before relying on it. An ID token is intended for that client; it should not simply be substituted for an API access token.

Read first
OAuth 2.0, Authentication
Related
JWT, SAML, Authorization code flow
Further reading
OpenID Connect Core 1.0, errata set 2
identity provider client app resource API ID token access token client presents access token issuer audience · client app time ID token validation identity accepted after validation
OpenID Connect adds an ID token for the client to validate before accepting a sign-in identity. Access tokens serve resource access. The diagram separates these purposes; the ID token is not a substitute for an API access token.

View in the full Protocols collection