OpenID Connect (OIDC)
What is OpenID Connect (OIDC)?
OpenID Connect (OIDC)An identity layer built on top of OAuth 2.0 that lets clients verify a user's identity and obtain basic profile information via signed ID tokens.
OpenID Connect (OIDC, Core 1.0 published 2014) extends OAuth 2.0 with a standardized authentication protocol. Where OAuth alone answers "what may this client access," OIDC answers "who is the user." Alongside the OAuth access token the authorization server issues an ID token — a signed JWT whose claims describe the authenticated user: iss (issuer), sub (stable subject identifier), aud (audience), exp/iat, nonce, and auth_time. A client must verify the signature against the provider's JWKS, confirm the issuer and that aud matches its own client ID, check expiry, and match the nonce it sent — skipping any of these turns the ID token into an attacker-forgeable string. Discovery (/.well-known/openid-configuration) and the UserInfo endpoint round out the protocol.
OIDC underpins "Sign in with Google/Microsoft/Apple," enterprise SSO, and federation. Its security hinges on correct token validation. In 2020 researcher Bhavuk Jain earned a $100,000 Apple bounty for a "Sign in with Apple" flaw: Apple's server would mint a valid JWT for any email address supplied, without confirming the requester owned it, so an attacker knowing a victim's email could have forged identity to relying parties — Apple found no evidence of in-the-wild abuse and patched it. The lesson recurs in OAuth/OIDC incidents: audience confusion, accepting alg: none, and missing nonce checks are the classic failure modes. Compared with SAML, OIDC is JSON/HTTP-native, mobile- and API-friendly, and supports PKCE, pairwise sub values, and DPoP sender-constrained tokens.
flowchart LR
U[User] --> C[Relying party app]
C -->|1. Auth request + scope=openid, nonce| AS[OpenID Provider]
AS -->|2. User authenticates / consents| U
AS -->|3. Authorization code| C
C -->|4. Code exchange| AS
AS -->|5. ID token JWT + access token| C
C --> V{Verify: signature via JWKS,<br/>iss, aud==client_id, exp, nonce}
V -- valid --> S[Establish session / identity]
V -- invalid --> R[Reject login]● Examples
- 01
A web app using "Sign in with Microsoft" via OIDC to authenticate corporate users.
- 02
A mobile app validating an ID token from Auth0 before granting access to user data.
● Frequently asked questions
What is OpenID Connect (OIDC)?
An identity layer built on top of OAuth 2.0 that lets clients verify a user's identity and obtain basic profile information via signed ID tokens. It belongs to the Identity & Access category of cybersecurity.
What does OpenID Connect (OIDC) mean?
An identity layer built on top of OAuth 2.0 that lets clients verify a user's identity and obtain basic profile information via signed ID tokens.
How do you defend against OpenID Connect (OIDC)?
Defences for OpenID Connect (OIDC) typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for OpenID Connect (OIDC)?
Common alternative names include: OIDC.