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

Signing is not hiding

04

Integrity and confidentiality solve different problems; nesting can combine them.

Related RFCs and changes

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

RFC 7519 · § 11.2EXAMPLE
4 / 4
Signing is not hidingA signature seal protects readable claims while a locked envelope represents encrypted plaintext; nesting combines them.Integrity and secrecy are different{ claims }readable JSONJWSreadable, protectedJWEencrypted plaintextnested: sign, then encrypt
04
Encrypt the signed token.

The outer encryption protects the inner signed token.

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

A signed payload can remain readable.

  • A JWS protects integrity through a signature or MAC, depending on its algorithm.
  • A JWE protects the plaintext through encryption and authenticated integrity.
  • For combined signing and encryption, this RFC normally recommends signing first and then encrypting.
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 ↗