Visual RFC.
ALL RFCs / RFC 7519
Read the RFC ↗
RFC 7519 / VALIDATION

Validation is a chain of checks

05

A token becomes usable only after parsing, cryptographic verification, and application checks succeed.

Related RFCs and changes

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

DIAGRAM§ 7.2 ↗
RFC 7519 · § 7.2EXAMPLE
4 / 4
Validation is a chain of checksA token moves through distinct parsing, cryptographic, claims, and application-policy gates.Validation has several gates✓Parse representation✓Verify signature / MAC✓Validate required claims✓Use under application policyA failed required gate rejects the token.
04
Only then authorize an action.

Cryptographic validity alone does not establish permission.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 7519 § 7.2RFC 8725 § 3

The JWT BCP strengthens implementation guidance: allowlist algorithms, validate issuer and audience, and use distinct validation rules for different token kinds.

Read the updated RFC section ↗
KEY POINT

Reject at the first failed required check.

  • Processing must reject a JWT if a required validation step fails.
  • The application determines acceptable algorithms; support for an algorithm does not imply it must be accepted.
  • Applications define required claims and the rules for their use.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗