Visual RFC.
ALL RFCs / RFC 7516
Read the RFC ↗
RFC 7516 / MECHANISMS

Five compact parts

01

A compact JWE represents a protected header, encrypted key, IV, ciphertext, and authentication tag.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 7516 · § 3.1EXAMPLE
3 / 3
Five compact partsA compact JWE represents a protected header, encrypted key, IV, ciphertext, and authentication tag. Current state: Authentication tag.Five compact partsheaderenc. keyIVciphertexttagfive period-separated partsauthenticateCompact layout is schematic; field sizes are not to scale.
03
Authentication tag

Integrity must validate before plaintext is accepted.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
JWT carried in JWERFC 8725 § 3.3

The JWT BCP makes clear that every applicable cryptographic operation must validate, including both outer and inner operations for nested JWTs.

Read the updated RFC section ↗
KEY POINT

Compact JWE uses five period-separated parts.

  • Compact JWE uses five period-separated parts.
  • The protected header remains readable.
  • The ciphertext hides the plaintext; base64url itself does not.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Five compact parts
  2. Content keys and recipient keys
  3. Associated data is checked too
  4. Several recipients, one ciphertext
  5. Decryption must authenticate
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗