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

Protected and unprotected headers

03

JWS JSON serialization can carry header values outside the signature’s protection.

Related RFCs and changes

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

DIAGRAM§ 3.2 ↗
RFC 7515 · § 3.2EXAMPLE
3 / 3
Protected and unprotected headersJWS JSON serialization can carry header values outside the signature’s protection. Current state: Consumer policy.Protected and unprotected headersprotected headeralg + parametersencoded in signing inputunprotected headeroutside signaturemutable metadatapolicy input?do not trust it as signed
03
Consumer policy

Do not treat unprotected metadata as authenticated instructions.

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

The protected header is integrity protected.

  • The protected header is integrity protected.
  • The unprotected header is not covered by that signature.
  • Header parameter names in the combined header must be disjoint.
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. What the signature covers
  2. Verification is a gate
  3. Protected and unprotected headers
  4. One payload, several signatures
  5. Authenticity does not stop replay
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗