JSON Web Token (JWT)
draft-ietf-oauth-json-web-token-03

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2012-07-30
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document Aug 2013
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
OAuth Working Group                                             M. Jones
Internet-Draft                                                 Microsoft
Intended status: Standards Track                              J. Bradley
Expires: January 31, 2013                                  Ping Identity
                                                             N. Sakimura
                                                                     NRI
                                                           July 30, 2012

                          JSON Web Token (JWT)
                   draft-ietf-oauth-json-web-token-03

Abstract

   JSON Web Token (JWT) is a means of representing claims to be
   transferred between two parties.  The claims in a JWT are encoded as
   a JavaScript Object Notation (JSON) object that is digitally signed
   or MACed using JSON Web Signature (JWS) and/or encrypted using JSON
   Web Encryption (JWE).

   The suggested pronunciation of JWT is the same as the English word
   "jot".

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 January 31, 2013.

Copyright Notice

   Copyright (c) 2012 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

Jones, et al.           Expires January 31, 2013                [Page 1]
Internet-Draft            JSON Web Token (JWT)                 July 2012

   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
   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.

Jones, et al.           Expires January 31, 2013                [Page 2]
Internet-Draft            JSON Web Token (JWT)                 July 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Notational Conventions . . . . . . . . . . . . . . . . . .  5
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  JSON Web Token (JWT) Overview  . . . . . . . . . . . . . . . .  6
     3.1.  Example JWT  . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  JWT Claims . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  Reserved Claim Names . . . . . . . . . . . . . . . . . . .  8
       4.1.1.  "exp" (Expiration Time) Claim  . . . . . . . . . . . .  8
       4.1.2.  "nbf" (Not Before) Claim . . . . . . . . . . . . . . .  9
       4.1.3.  "iat" (Issued At) Claim  . . . . . . . . . . . . . . .  9
       4.1.4.  "iss" (Issuer) Claim . . . . . . . . . . . . . . . . .  9
       4.1.5.  "aud" (Audience) Claim . . . . . . . . . . . . . . . .  9
       4.1.6.  "prn" (Principal) Claim  . . . . . . . . . . . . . . .  9
       4.1.7.  "jti" (JWT ID) Claim . . . . . . . . . . . . . . . . . 10
       4.1.8.  "typ" (Type) Claim . . . . . . . . . . . . . . . . . . 10
     4.2.  Public Claim Names . . . . . . . . . . . . . . . . . . . . 10
     4.3.  Private Claim Names  . . . . . . . . . . . . . . . . . . . 10
   5.  JWT Header . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     5.1.  "typ" (Type) Header Parameter  . . . . . . . . . . . . . . 11
     5.2.  "cty" (Content Type) Header Parameter  . . . . . . . . . . 11
   6.  Plaintext JWTs . . . . . . . . . . . . . . . . . . . . . . . . 11
     6.1.  Example Plaintext JWT  . . . . . . . . . . . . . . . . . . 11
   7.  Rules for Creating and Validating a JWT  . . . . . . . . . . . 12
   8.  Cryptographic Algorithms . . . . . . . . . . . . . . . . . . . 14
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
     9.1.  JSON Web Token Claims Registry . . . . . . . . . . . . . . 15
       9.1.1.  Registration Template  . . . . . . . . . . . . . . . . 16
Show full document text