JSON Web Token (JWT), May 2015
- File formats:
- PROPOSED STANDARD
- Updated by:
- RFC 7797, RFC 8725
- M. Jones
- oauth (sec)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7519
JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.