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

Associated data is checked too

03

Authenticated encryption binds protected metadata as well as the encrypted content.

Related RFCs and changes

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

DIAGRAM§ 5.2 ↗
RFC 7516 · § 5.2EXAMPLE
3 / 3
Associated data is checked tooAuthenticated encryption binds protected metadata as well as the encrypted content. Current state: Changed metadata.Associated data is checked tooprotected headerassociated dataciphertext + tagAEAD checkChanged protected metadata → reject
03
Changed metadata

A protected-header modification makes verification fail.

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

The encoded protected header contributes to authenticated additional data.

  • The encoded protected header contributes to authenticated additional data.
  • JSON serialization can also carry explicit additional authenticated data.
  • Any required authentication failure rejects the JWE.
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

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 ↗