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

Public and private are different

04

A public key representation can be shared; private and symmetric key material must remain confidential.

Related RFCs and changes

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

DIAGRAM§ 9.2 ↗
RFC 7517 · § 9.2EXAMPLE
3 / 3
Public and private are differentA public key representation can be shared; private and symmetric key material must remain confidential. Current state: Publish safely.Public and private are differentpublic JWKn: …e: AQABprivate JWKn / e / d: SECRETpublish only publicSymmetric k material is secret too.
03
Publish safely

Remove private members before publishing the public key set.

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

Private JWKs contain additional secret members.

  • Private JWKs contain additional secret members.
  • A symmetric key’s k member is itself secret key material.
  • Prevent disclosure of non-public JWK members.
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 ↗