Proof-Of-Possession Semantics for JSON Web Tokens (JWTs)
draft-ietf-oauth-proof-of-possession-01

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Authors Michael Jones  , John Bradley  , Hannes Tschofenig 
Last updated 2015-03-04 (latest revision 2015-01-28)
Replaces draft-jones-oauth-proof-of-possession
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Derek Atkins
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Derek Atkins" <derek@ihtfp.com>
OAuth Working Group                                             M. Jones
Internet-Draft                                                 Microsoft
Intended status: Standards Track                              J. Bradley
Expires: August 1, 2015                                    Ping Identity
                                                           H. Tschofenig
                                                             ARM Limited
                                                        January 28, 2015

        Proof-Of-Possession Semantics for JSON Web Tokens (JWTs)
                draft-ietf-oauth-proof-of-possession-01

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.  This property 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 August 1, 2015.

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
   to this document.  Code Components extracted from this document must

Jones, et al.            Expires August 1, 2015                 [Page 1]
Internet-Draft        proof-of-possession for JWTs          January 2015

   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 . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Proof-Of-Possession Representation . . . . . . . . . . . . . .  4
     3.1.  Proof-of-Possession of an Asymmetric Key . . . . . . . . .  4
     3.2.  Proof-of-Possession of a Symmetric Key . . . . . . . . . .  5
     3.3.  Confirmation . . . . . . . . . . . . . . . . . . . . . . .  6
     3.4.  Specifics Intentionally Not Specified  . . . . . . . . . .  6
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  6
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
     5.1.  JSON Web Token Claims Registration . . . . . . . . . . . .  8
       5.1.1.  Registry Contents  . . . . . . . . . . . . . . . . . .  8
     5.2.  JWT Confirmation Methods Registry  . . . . . . . . . . . .  8
       5.2.1.  Registration Template  . . . . . . . . . . . . . . . .  9
       5.2.2.  Initial Registry Contents  . . . . . . . . . . . . . .  9
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     6.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Open Issues . . . . . . . . . . . . . . . . . . . . . 10
   Appendix B.  Acknowledgements  . . . . . . . . . . . . . . . . . . 10
   Appendix C.  Document History  . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11

Jones, et al.            Expires August 1, 2015                 [Page 2]
Internet-Draft        proof-of-possession for JWTs          January 2015

1.  Introduction

   This specification defines how to express a declaration in a JSON Web
   Token (JWT) [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.  This property is
   also sometimes described as the presenter being a holder-of-key.

   [[ Editorial Note: This paragraph needs to be updated to provide more
   context and possibly also to describe the use of asymmetric keys
   instead.  It's not clear that the symmetric case is as useful or
   valuable, and it is certainly more complicated.]]  Envision the
   following use case: An OAuth 2.0 authorization server generates a JWT
Show full document text