RFC 7800: Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
In plain English — editorial summary, not part of the RFC
This specification describes how to declare in a JSON Web Token (JWT) that the presenter of the JWT possesses a particular proof-of- possession key and how the recipient can cryptographically confirm proof of possession of the key by the presenter. Being able to prove possession of a key is also sometimes described as the presenter being a holder-of-key.
Document record
- Document ID
- RFC7800
- Published
- April 2016
- Authors
- M. Jones; J. Bradley; H. Tschofenig
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 2020
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8747Proof-of-Possession Key Semantics for CBOR Web Tokens (CWTs)Current
March 2020
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?