OpenID Connect
Subject: Computer and Technology noun /ˌoʊ.pən.aɪˈdiː kəˈnɛkt/ 1 definition
- identity-management
- user-authentication
- web-security
- information-security
-
Definition (noun)
Entry #323 · UpdatedOpenID Connect (OIDC) is an open identity authentication protocol built as a standardized layer on top of the OAuth 2.0 authorization framework. It enables a client application, known as a Relying Party (RP), to verify an end user's identity through an OpenID Provider (OP) without directly collecting or storing the user's password. After authenticating the user, the OpenID Provider issues an ID Token—a JSON Web Token (JWT) containing standardized claims about the authentication event—whose signature, issuer, audience, and expiration the Relying Party validates before optionally querying a RESTful UserInfo endpoint for additional profile attributes. Designed for modern web, single-page, and mobile applications as a lightweight JSON and REST alternative to XML-based SAML, OIDC strictly handles user authentication and identity claims while leaving delegated resource authorization to OAuth 2.0 access tokens and application-level access controls.
Common Forms
Authorization Code Flow: Redirects the user to the OpenID Provider and returns a short-lived authorization code that the client exchanges over a back-channel at the token endpoint for an ID Token and access token; paired with Proof Key for Code Exchange (PKCE), it serves as the recommended default for server-side web apps, single-page apps, and native mobile clients.
Implicit Flow: Returns the ID Token and optional access token directly to the client in the browser redirect URI fragment without a back-channel token exchange; originally created for browser-only JavaScript applications, it is now widely superseded by the Authorization Code Flow with PKCE to avoid exposing tokens in browser history and URLs.
Hybrid Flow: Combines front-channel and back-channel interactions by returning an ID Token immediately in the authorization response alongside an authorization code, allowing the client to inspect initial identity claims right away while still redeeming the code securely at the token endpoint for refresh tokens or additional claims.
Client-Initiated Backchannel Authentication (CIBA): Decouples the device requesting login from the device authenticating the user by letting a backend client initiate an out-of-band verification prompt—such as a mobile push notification—without relying on browser redirects.
Example
When a user clicks "Sign in with Google" on a web application, the app discovers the provider's endpoints via
/.well-known/openid-configurationand redirects the browser to the authorization endpoint withscope=openid profile email,response_type=code, anonce, and a PKCEcode_challenge. After the user authenticates, the app exchanges the returned authorization code andcode_verifierat the provider's token endpoint for anid_tokenJWT, verifies itsRS256signature against the provider's JWKS keys along with theiss,aud, andnonceclaims, and signs the user in under their uniquesubidentifier.