RFC 9278: JWK Thumbprint URI
In plain English — editorial summary, not part of the RFC
This specification registers a kind of URI that represents a JSON Web Key (JWK) Thumbprint value. JWK Thumbprints are defined in RFC 7638. This enables JWK Thumbprints to be used, for instance, as key identifiers in contexts requiring URIs.
Document record
- Document ID
- RFC9278
- Published
- August 2022
- Authors
- M. Jones; K. Yasuda
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7638JSON Web Key (JWK) ThumbprintCurrent
September 2015
- RFC 7520Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE)Current
May 2015
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 7517JSON Web Key (JWK)Current
May 2015
- RFC 7516JSON Web Encryption (JWE)Current
May 2015
- RFC 7515JSON Web Signature (JWS)Current
May 2015
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
- RFC 6755An IETF URN Sub-Namespace for OAuthCurrent
October 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?