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

A key has typed members

01

A JWK is a JSON object representing a cryptographic key and optional metadata.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 7517 · § 4EXAMPLE
3 / 3
A key has typed membersA JWK is a JSON object representing a cryptographic key and optional metadata. Current state: Metadata.A key has typed memberskty: RSAn: moduluse: exponentkid: key-1Metadata does not establish key provenance
03
Metadata

kid and alg help identify intended use but do not create trust.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 7517 key identifiersRFC 7638 § 3

A separate RFC defines thumbprints from required key members in a canonical representation, providing a reproducible identifier rather than relying on an arbitrary kid.

Read the updated RFC section ↗
KEY POINT

kty identifies the key type.

  • kty identifies the key type.
  • Algorithm-specific members carry the actual key material.
  • Metadata is not a substitute for authenticated key provenance.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗