Protocols
Saved & recent

JWT

Also called: JSON Web Token

A JSON Web Token is a compact representation of claims, such as a subject, issuer, audience, or expiry. JWTs can be protected with a signature or message authentication code, encrypted, or nested. A common signed compact JWT has three base64url-encoded parts: header, payload, and signature.

For example, a service receiving a signed token must validate the accepted cryptographic protection and the claims required by its token profile. Decoding the payload does not validate it. Encoding also does not make it secret: readable signed claims require encryption if confidentiality is needed.

Related
OpenID Connect, OAuth 2.0, Authorization, JSON Web Key Set, JWT claims validation
Further reading
RFC 7519 — JSON Web Token (JWT)
signed compact form · schematic header payload signature . . decoded payload iss: "issuer.example" sub: "user-7" aud: "catalogue" signature + profile check separate validation readable without decryption decoding and validation
A signed compact JWT has header, payload and signature segments. Decoding reveals illustrative claims; validation separately checks cryptographic protection and required claims. These three segments do not describe encrypted JWTs, and signed payloads are not secret.

View in the full Protocols collection