OpenID Connect
— OpenID Connect Core 1.0OpenID Connect adds authentication to OAuth 2.0 authorization. A relying party sends the user to an OpenID Provider, receives an authorization code, and exchanges it for an ID token whose signature, issuer, audience, and nonce it verifies before trusting the identity.
Interactive Session: How OpenID Connect Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of OpenID Connect.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
Redirect URI abuse
Credential attackA loose redirect URI allowlist sends the authorization code to an attacker-controlled endpoint.
Craft the request
The attacker builds an authorization request using an allowed but open redirect.
Authorize requests with unexpected redirect parameters.
Account takeover through stolen authorization codes.
Defences that matter
- Exact redirect URI matching
- PKCE for all public clients
- State and nonce validation
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- ID token implemented as a signed JSON Web Token with standard claims
- Discovery document at /.well-known/openid-configuration and published JWKS keys
- Authorization Code Flow with PKCE plus implicit and hybrid response types
- Standard scopes such as openid, profile, email, and optional UserInfo endpoint
Real-World Use Cases
- Social login with Google, Microsoft, or Apple accounts
- Single sign-on across SaaS applications through a central identity provider
- Mobile and single-page apps that need verified user identity tokens
Advantages & Strengths
- Simple JSON and JWT formats that are easy for web and mobile clients to consume
- Built directly on OAuth 2.0, so one token stack covers authorization and identity
Limitations & Vulnerabilities
- Clients must carefully validate issuer, audience, signature, and nonce or they accept forged tokens
- Implicit flow and loose redirect URI rules have caused real-world token leaks