ID token
The signed token in OpenID Connect that tells a client who the user is and how they authenticated, meant for the client rather than for APIs.
In more detail
Do not send it to an API as an access token: its audience is the client. Verify it like any other signed token before using its claims.
Related terms
- OpenID Connect — An identity layer on top of OAuth 2.0 that tells an application who signed in, using a signed ID token.
- access token — A generated string that proves who you are to a service, used instead of a password and revocable on its own.
- audience — The recipient a token is meant for, named in its aud claim, such as one particular API.
- JSON Web Token — A compact signed token made of three base64url parts separated by dots: a header, a payload of claims and a signature.
- claim — One statement inside a token, as a name and value, such as sub (subject), exp (expiry), iss (issuer), aud (audience) or scope.
Taught in
- OAuth Two And OpenID Connect — Modern API Architecture: REST, GraphQL & gRPC
- Workload Identity Federation: Eliminating Static Keys — Cloud Security & DevSecOps Engineering
- Zero-Trust Network Access & IdP Federation — Cloud Security & DevSecOps Engineering
- OAuth2 & OpenID Connect: Social Auth & PKCE Flows — Production Full-Stack Engineering