NEW
Also known as: OIDC
An authentication protocol adding a simple identity layer on top of OAuth 2.0 using ID tokens and standardized endpoints.
DESCRIPTION
OpenID Connect standardizes user authentication and identity exchange using OAuth 2.0 flows. It defines ID tokens, discovery, and UserInfo endpoints for interoperable sign-in. OIDC supports modern web and mobile clients with security features like nonce and PKCE. Widely adopted by identity providers, it enables SSO and federation across services. Correct claim validation and configuration are essential for secure deployments.
ALTERNATIVE DEFINITIONS
OpenID Foundation
OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol.
Concise specification definition highlighting identity layer.
Wikipedia
OpenID Connect (OIDC) is an authentication protocol, based on the OAuth 2.0 family of specifications.
Positions OIDC within OAuth 2.0-based protocols.
Auth0
OpenID Connect uses ID tokens that contain user identity information to authenticate users and communicate their identity to clients.
Highlights the role of ID tokens carrying identity claims.
RELATED TERMS
OAuth 2.0 Identity Provider ID Token Authorization Code Flow Discovery UserInfo Endpoint JWKS Claims Multi-Factor Authentication
COMPETING TERMS
SAML 2.0 WS-Federation
KNOWLEDGE AREAS
Data Security Software Engineering Cloud Platform & Tooling
TARGET AUDIENCE
Software Developer DevOps Engineer Cloud Architect Data Engineer Chief Information Officer Chief Technology Officer AI Engineer
EXTERNAL SOURCES
- Wikipedia - OpenID Connect
- OpenID Foundation - Core OIDC specification
- Auth0 - ID token structure and validation
- Okta Developer - Authorization code with PKCE for OIDC
TOP QUESTIONS
What does OpenID Connect add to OAuth 2.0?
OIDC defines standardized authentication with ID tokens, discovery, and UserInfo endpoints atop OAuth authorization.
Category: Topic
What is an ID token in OpenID Connect?
It’s a JWT carrying identity claims like subject, issuer, and authentication details for the user.
Category: Example
Which OIDC flow should I use?
Use authorization code with PKCE for web/mobile clients; implicit is deprecated for security reasons.
Category: Requirements
How do you validate OIDC tokens?
Verify signature using JWKS, check issuer, audience, nonce, expiry, and required claims.
Category: Management
What are common OpenID Connect mistakes?
Not validating nonce, misusing implicit flow, and failing to rotate signing keys can expose sessions.
Category: Mistakes
How does OIDC compare to SAML 2.0?
OIDC uses JSON and OAuth flows; SAML uses XML assertions and is prevalent in legacy enterprise SSO.
Category: Alternatives
Is OpenID Connect suitable for mobile apps?
Yes. It pairs with PKCE to secure authorization code flows on public clients.
Category: Relevancy
What is OIDC discovery?
A standard endpoint that publishes provider configuration to simplify client setup.
Category: Example
How do you start implementing OpenID Connect?
Choose an IdP, register a client, implement the auth code with PKCE, and validate ID tokens and claims.
Category: Requirements