RFC 7519 - JSON Web Token (JWT)
Published: May 2015
Status: Standards Track
Authors: M. Jones (Microsoft), J. Bradley (Ping Identity), N. Sakimura (NRI)
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at ````http://www.rfc-editor.org/info/rfc7519\````.
Table of Contents
- 1. Introduction
- 1.1. Notational Conventions
- 2. Terminology
- 3. JSON Web Token (JWT) Overview
- 3.1. Example JWT
- 4. JWT Claims
- 4.1. Registered Claim Names
- 4.2. Public Claim Names
- 4.3. Private Claim Names
- 5. JOSE Header
- 5.1. "typ" (Type) Header Parameter
- 5.2. "cty" (Content Type) Header Parameter
- 5.3. Replicating Claims as Header Parameters
- 6. Unsecured JWTs
- 6.1. Example Unsecured JWT
- 7. Creating and Validating JWTs
- 7.1. Creating a JWT
- 7.2. Validating a JWT
- 7.3. String Comparison Rules
- 8. Implementation Requirements
- 9. URI for Declaring that Content is a JWT
- 10. IANA Considerations
- 10.1. JSON Web Token Claims Registry
- 10.2. Sub-Namespace Registration
- 10.3. Media Type Registration
- 10.4. Header Parameter Names Registration
- 11. Security Considerations
- 11.1. Trust Decisions
- 11.2. Signing and Encryption Order
- 12. Privacy Considerations
- 13. References
- 13.1. Normative References
- 13.2. Informative References
Appendices
- Appendix A. JWT Examples
- A.1. Example Encrypted JWT
- A.2. Example Nested JWT
- Appendix B. Relationship of JWTs to SAML Assertions
- Appendix C. Relationship of JWTs to Simple Web Tokens
Related Resources
- Official Text: RFC 7519
- Official Page: RFC 7519 DataTracker
- Errata: RFC Editor Errata
Acknowledgements
This specification is based on earlier work on JSON Web Token (JWT) and Simple Web Token (SWT). Thanks to all the working group members who contributed to this standard.
Copyright Notice
Copyright (c) 2015 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 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.