RFC 7797

JSON Web Signature (JWS) Unencoded Payload Option, February 2016

Canonical URL:
https://www.rfc-editor.org/rfc/rfc7797.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Updates:
RFC 7519
Author:
M. Jones
Stream:
IETF
Source:
jose (sec)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC7797

Discuss this RFC: Send questions or comments to jose@ietf.org

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

JSON Web Signature (JWS) represents the payload of a JWS as a base64url-encoded value and uses this value in the JWS Signature computation. While this enables arbitrary payloads to be integrity protected, some have described use cases in which the base64url encoding is unnecessary and/or an impediment to adoption, especially when the payload is large and/or detached. This specification defines a means of accommodating these use cases by defining an option to change the JWS Signing Input computation to not base64url- encode the payload. This option is intended to broaden the set of use cases for which the use of JWS is a good fit. This specification updates RFC 7519 by stating that JSON Web Tokens (JWTs) MUST NOT use the unencoded payload option defined by this specification.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×