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

Verification is a gate

02

A consumer verifies the signature or MAC before treating the protected content as authenticated.

Related RFCs and changes

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

DIAGRAM§ 5.2 ↗
RFC 7515 · § 5.2EXAMPLE
3 / 3
Verification is a gateA consumer verifies the signature or MAC before treating the protected content as authenticated. Current state: Reject a mismatch.Verification is a gateprotected bytessignature / MACverifycryptographic checkmodified bytesMismatch → reject
03
Reject a mismatch

Do not pass modified content through to trusted processing.

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

The application determines acceptable algorithms.

  • The application determines acceptable algorithms.
  • An invalid cryptographic check rejects that JWS.
  • A valid signature does not establish that its key is trusted for every purpose.
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 ↗