JSON Web Signature (JWS) Unencoded Payload Option
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 11
- 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.
- Publication Date
- 2016-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7797- Link
- https://doi.org/10.17487/RFC7797
- Author(s)
- Michael B. Jones
- Keyword(s)
- JSON, JOSE, JWS, Digital Signature, Message Authentication Code, MAC
Latest version of IETF RFC 7797
Document Versions — IETF RFC 7797
-
▶ IETF RFC 7797 (2016-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- The Unicode Consortium, "The Unicode Standard", < http://www.unicode.org/versions/latest/ >. EXTERNAL
- IANA, "JSON Object Signing and Encryption (JOSE)", < http://www.iana.org/assignments/jose >. EXTERNAL
- IETF RFC 20 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3629 [Active*]
- IETF RFC 7159 [Superseded*]
- IETF RFC 7515 [Active*]
- RFC7518 — JWA EXTERNAL
- IETF RFC 7519 [Active*]
Bibliographic Reference(s)
- IETF RFC 3986 [Active, Amended*]
- RFC7517 — JWK EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7797.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7797, JSON Web Signature (JWS) Unencoded Payload Option. Available at https://doi.org/10.17487/RFC7797
Snippet:
IETF RFC 7797, JSON Web Signature (JWS) Unencoded Payload Option. Available at https://doi.org/10.17487/RFC7797
HTML (ISO 690 compliant)
Preview:
IETF RFC 7797, JSON Web Signature (JWS) Unencoded Payload Option. Available at https://doi.org/10.17487/RFC7797
Snippet:
<span class="citation"><cite>IETF RFC 7797</cite>, JSON Web Signature (JWS) Unencoded Payload Option. Available at <a href="https://doi.org/10.17487/RFC7797" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7797</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7797, JSON Web Signature (JWS) Unencoded Payload Option
doi: 10.17487/RFC7797
url: https://doi.org/10.17487/RFC7797
doi: 10.17487/RFC7797
url: https://doi.org/10.17487/RFC7797
Snippet:
<li> <cite id="bib-rfc7797">IETF RFC 7797</cite>, JSON Web Signature (JWS) Unencoded Payload Option <span class="doi">10.17487/RFC7797</span> </li>