Visual RFC.
ALL RFCs / RFC 7519
Read the RFC ↗
RFC 7519 / TOKEN ANATOMY

A compact token comes apart

01

A JWT carries a JSON claims set inside a JWS or JWE representation.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3 ↗
RFC 7519 · § 3EXAMPLE
4 / 4
A compact token comes apartThree compact JWS parts open into header and claim text, followed by a signature or MAC check.A signed JWT: three parts, two dotseyJhbGci…header·eyJzdWIi…payload·SflKxwR…signaturealg: HS256operation hintsub: user-42asserted claimCheck the protected bytes with a trusted keyDecoding makes text readable. Verification checks protection.
04
Authenticate the protected bytes.

Use the intended algorithm and a trusted, appropriate key.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Decoding is not verification.

  • Compact JWS has three period-separated parts; compact JWE has five.
  • Base64url is an encoding, not encryption.
  • A JOSE header describes the cryptographic operation; it is not a trusted policy by itself.
DETAILS

The examples simplify the wire representation. Follow the linked specification and application profile for implementation.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A compact token comes apart
  2. Claims live on a timeline
  3. Who said it, and who is it for?
  4. Signing is not hiding
  5. Validation is a chain of checks
  6. Trust comes from outside the token
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗