JSON Web Token (JWT)

Document Type Replaced Internet-Draft (individual)
Authors Michael Jones  , Dirk Balfanz  , John Bradley  , Yaron Goland  , John Panzer  , Nat Sakimura  , Paul Tarjan 
Last updated 2013-04-19 (latest revision 2012-05-12)
Replaced by RFC 7519
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-oauth-json-web-token
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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


Michael Jones (mbj@microsoft.com)
Dirk Balfanz (balfanz@google.com)
John Bradley (ve7jtb@ve7jtb.com)
Yaron Goland (yarong@microsoft.com)
John Panzer (jpanzer@google.com)
Nat Sakimura (n-sakimura@nri.co.jp)
Paul Tarjan (pt@fb.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)