OpenID Connect Overview and Relationship to OAuth 2.0
You'll learn: How OpenID Connect (OIDC) extends OAuth 2.0 to provide true authentication, not just authorization.
The Authentication Gap in OAuth 2.0
Remember that OAuth 2.0 is fundamentally an authorization framework — it answers "What can this application access?" not "Who is this user?" When an app gets an access token from OAuth 2.0, it knows it can call APIs, but doesn't reliably know who granted permission.
Think of it like getting a hotel key card: the card opens doors (authorization), but doesn't prove your identity. You could have borrowed someone else's card.
Enter OpenID Connect
OpenID Connect (OIDC) is an identity layer built on top of OAuth 2.0. It uses the same OAuth 2.0 flows you've learned (like Authorization Code Flow with PKCE) but adds standardized mechanisms for authentication.
Key Additions OIDC Brings:
- ID Token: A signed JWT containing user identity claims (name, email, subject ID)
- UserInfo Endpoint: A standardized API to retrieve additional user profile information
- Standard Scopes: The
openidscope triggers OIDC behavior; optional scopes likeprofileandemailrequest specific claims - Claims: Structured identity attributes with defined meanings
Why This Matters
OAuth 2.0 alone leaves authentication as an implementation detail — different providers do it differently. OIDC standardizes how applications receive and verify user identity information, making "Sign in with Google/Microsoft/etc." work consistently.
Key Takeaway: OpenID Connect extends OAuth 2.0 from "permission delegation" to "authentication + permission delegation" by adding ID tokens and standardized identity claims, solving the "who is the user?" problem that OAuth 2.0 intentionally doesn't address.