RFC 7516: JSON Web Encryption (JWE)
In plain English — editorial summary, not part of the RFC
JSON Web Encryption (JWE) represents encrypted content using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries defined by that specification. Related digital signature and Message Authentication Code (MAC) capabilities are described in the separate JSON Web Signature (JWS) specification.
Document record
- Document ID
- RFC7516
- Published
- May 2015
- Authors
- M. Jones; J. Hildebrand
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 51
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7517JSON Web Key (JWK)Current
May 2015
- RFC 7515JSON Web Signature (JWS)Current
May 2015
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 7520Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE)Current
May 2015
- RFC 7797JSON Web Signature (JWS) Unencoded Payload OptionCurrent
February 2016
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 7165Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)Current
April 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?