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

Protect a stored key object

05

A JWK or JWK Set can itself be encrypted using JWE.

Related RFCs and changes

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

DIAGRAM§ 7 ↗
RFC 7517 · § 7EXAMPLE
3 / 3
Protect a stored key objectA JWK or JWK Set can itself be encrypted using JWE. Current state: Authorized recovery.Protect a stored key objectprivate JWKsecret membersJWEencrypted keyjwk+jsonauthorized recovery
03
Authorized recovery

Decrypt and authenticate before exposing key material to the intended operation.

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

Encryption protects serialized key information only when the surrounding key-management design is sound.

  • Encryption protects serialized key information only when the surrounding key-management design is sound.
  • The protected content type identifies jwk+json or jwk-set+json.
  • Authenticated provenance and permission checks still matter after decryption.
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. A key has typed members
  2. Choose from a JWK Set
  3. Use and operations constrain keys
  4. Public and private are different
  5. Protect a stored key object

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 ↗