Protocols
Saved & recent

JWT claims validation

Also called: JWT validation, claim validation

JWT claims validation asks whether a cryptographically valid token is acceptable for this application and request. A verifier uses allowed algorithms and trusted keys, then checks the required issuer, audience, time bounds and token purpose. Merely decoding JSON proves nothing. Required claims and rules come from the token’s application profile.

For example, a billing API rejects a correctly signed token whose aud identifies the photo API. It also rejects an expired token and does not substitute an OpenID Connect ID token for its expected access token. Claims such as exp and nbf have defined time meanings, but not every JWT profile requires the same claim set.

Read first
JWT
Related
JWT, JSON Web Key Set, OpenID Connect
Further reading
allowed algorithm signature valid checks continue issuer audience mismatch time purpose token: photo-api expected: billing-api rejected · audience mismatch profile-dependent claim checks
The signature and issuer pass, but this billing API rejects the photo-api audience. Time bounds and token purpose are additional gates for tokens that pass earlier checks; exact claim requirements depend on the application profile.

View in the full Protocols collection