JSON Web Token (JWT)
draft-jones-json-web-token-10
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-04-19 (latest revision 2012-05-12) | ||
| Replaced by | RFC 7519 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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) | ||
https://www.ietf.org/archive/id/draft-jones-json-web-token-10.txt
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 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".
Authors
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.)