Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
draft-ietf-oauth-proof-of-possession-05
OAuth Working Group M. Jones
Internet-Draft Microsoft
Intended status: Standards Track J. Bradley
Expires: April 21, 2016 Ping Identity
H. Tschofenig
ARM Limited
October 19, 2015
Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)
draft-ietf-oauth-proof-of-possession-05
Abstract
This specification defines how to express a declaration in a JSON Web
Token (JWT) that the presenter of the JWT possesses a particular key
and that 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.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 21, 2016.
Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Jones, et al. Expires April 21, 2016 [Page 1]
Internet-Draft Proof-of-Possession Key for JWTs October 2015
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Representations for Proof-of-Possession Keys . . . . . . . . . 4
3.1. Confirmation Claim . . . . . . . . . . . . . . . . . . . . 5
3.2. Representation of an Asymmetric Proof-of-Possession Key . 6
3.3. Representation of an Encrypted Symmetric
Proof-of-Possession Key . . . . . . . . . . . . . . . . . 6
3.4. Representation of a Key ID for a Proof-of-Possession
Key . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.5. Representation of a URL for a Proof-of-Possession Key . . 8
3.6. Specifics Intentionally Not Specified . . . . . . . . . . 8
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6.1. JSON Web Token Claims Registration . . . . . . . . . . . . 11
6.1.1. Registry Contents . . . . . . . . . . . . . . . . . . 11
6.2. JWT Confirmation Methods Registry . . . . . . . . . . . . 11
6.2.1. Registration Template . . . . . . . . . . . . . . . . 11
6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 12
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . . 13
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 14
Appendix B. Document History . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15
Jones, et al. Expires April 21, 2016 [Page 2]
Internet-Draft Proof-of-Possession Key for JWTs October 2015
1. Introduction
This specification defines how a JSON Web Token (JWT) [JWT] can
declare that the presenter of the JWT possesses a key and that the
recipient can cryptographically confirm that the presenter possesses
that key. Proof-of-possession of a key is also sometimes described
as the presenter being a holder-of-key. The
[I-D.ietf-oauth-pop-architecture] specification describes key
Show full document text