JSON Web Token (JWT)
draft-jones-json-web-token-10
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Jones , Dirk Balfanz , John Bradley , Yaron Y. Goland , John Panzer , Nat Sakimura , Paul Tarjan | ||
| Last updated | 2013-04-19 (Latest revision 2012-05-12) | ||
| Replaced by | RFC 7519 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Dirk Balfanz
John Bradley
Yaron Y. Goland
John Panzer
Nat Sakimura
Paul Tarjan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)