OpenID Connect: Adding Identity to OAuth 2.0
You'll learn how OpenID Connect builds on OAuth 2.0 to provide not just authorization, but also authentication and user identity information.
The Gap OAuth 2.0 Leaves
OAuth 2.0 is excellent for authorization—letting apps access resources on your behalf. However, it doesn't actually tell the app who you are. It only provides access tokens that grant permissions. If an app needs to know your identity (email, name, profile picture), OAuth 2.0 alone doesn't standardize that.
Enter OpenID Connect (OIDC)
OpenID Connect is a simple identity layer built on top of OAuth 2.0. It extends the OAuth flow to include authentication, allowing clients to verify a user's identity and obtain basic profile information in a standardized way.
Think of it this way: OAuth 2.0 is like getting a valet parking ticket (authorization to retrieve your car), while OpenID Connect is like showing your driver's license first (authentication proving who you are) and then getting the ticket.
How It Works
OIDC adds an ID Token alongside OAuth's access token. This ID Token is a JSON Web Token (JWT) containing verified claims about the authenticated user—their unique identifier, email, name, and when they authenticated. The authorization server (now called an OpenID Provider) issues this token during the OAuth flow.
When you use "Sign in with Google" or "Login with GitHub," you're likely using OpenID Connect. The app receives proof of your identity (ID Token) and optionally an access token to fetch additional profile data from a standardized /userinfo endpoint.
Key Takeaway: OpenID Connect extends OAuth 2.0 with an identity layer, providing standardized authentication via ID Tokens that contain verified user identity claims, solving the "who is this user?" problem OAuth 2.0 doesn't address.