Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 7519

Author:

M. Jones

Stream:

IETF

Source:

jose (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7797

Discuss this RFC: Send questions or comments to the mailing listjose@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7797

Abstract

JSON Web Signature (JWS) represents the payload of a JWS as abase64url-encoded value and uses this value in the JWS Signaturecomputation. While this enables arbitrary payloads to be integrityprotected, some have described use cases in which the base64urlencoding is unnecessary and/or an impediment to adoption, especiallywhen the payload is large and/or detached. This specificationdefines a means of accommodating these use cases by defining anoption to change the JWS Signing Input computation to not base64url-encode the payload. This option is intended to broaden the set ofuse 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 thisspecification.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.