liveBook · Manning

OpenID Connect ID token

As explained in ASP.NET Core in Action, 3e

An ID token is an OpenID Connect token that describes a user authentication event and may contain claims about the authenticated user.

An ID token describes a user authentication event in OpenID Connect and may carry claims about the authenticated user. It is a bearer token, but its purpose differs from an access token: an access token authorizes access to a resource, while an ID token communicates authentication information. section 25.2 section 25.2

Keep these token roles separate:

  • Use an access token to authorize access to a protected resource. section 25.2
  • Use an ID token to describe the authentication event and authenticated-user claims. section 25.2
  • Treat bearer tokens according to their purpose rather than assuming that every bearer token authorizes an API request. section 25.2

How ASP.NET Core in Action, 3e covers it

How deep it goes
Defines the token’s purpose and contrasts it with access tokens, without detailing its complete validation or issuance flow.
Examples
Uses a decoded JWT example to show header, payload, signature, and the need for signature verification.
What you can do after
Evaluate whether a token communicates authentication or authorizes access to a resource.
How it connects
Connects OpenID Connect, bearer tokens, access tokens, identity claims, and authentication.

Also explained in

Compare how 3 books explain OpenID Connect ID token →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.