JWS Clear Text JSON Signature Option (JWS/CT)
draft-jordan-jws-ct-02
Network Working Group B. Jordan, Ed.
Internet-Draft Broadcom
Intended status: Informational S. Erdtman
Expires: 30 July 2021 Spotify AB
A. Rundgren
Independent
26 January 2021
JWS Clear Text JSON Signature Option (JWS/CT)
draft-jordan-jws-ct-02
Abstract
This document describes a method for extending the scope of the JSON
Web Signature (JWS) standard, called JWS/CT. By combining the
detached mode of JWS with the JSON Canonicalization Scheme (JCS),
JWS/CT enables JSON objects to remain in the JSON format after being
signed (aka "Clear Text" signing). In addition to supporting a
consistent data format, this arrangement also simplifies
documentation, debugging, and logging. The ability to embed signed
JSON objects in other JSON objects, makes the use of counter-
signatures straightforward.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 30 July 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
Jordan, et al. Expires 30 July 2021 [Page 1]
Internet-Draft JWS/CT January 2021
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Detailed Operation . . . . . . . . . . . . . . . . . . . . . 3
3.1. Signature Creation . . . . . . . . . . . . . . . . . . . 4
3.1.1. Create the JSON Object to be Signed . . . . . . . . . 4
3.1.2. Canonicalize the JSON Object to be Signed . . . . . . 4
3.1.3. Generate a JWS String . . . . . . . . . . . . . . . . 5
3.1.4. Assemble the Signed JSON Object . . . . . . . . . . . 5
3.2. Signature Validation . . . . . . . . . . . . . . . . . . 6
3.2.1. Parse the Signed JSON Object . . . . . . . . . . . . 6
3.2.2. Fetch the Signature Property String . . . . . . . . . 6
3.2.3. Remove the Signature Property String . . . . . . . . 6
3.2.4. Canonicalize the Remaining JSON Object . . . . . . . 7
3.2.5. Validate the JWS String . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Open-Source Implementations . . . . . . . . . . . . 10
Appendix B. JWS/CT Application Notes . . . . . . . . . . . . . . 10
B.1. Counter Signatures . . . . . . . . . . . . . . . . . . . 10
B.2. Detached Signatures . . . . . . . . . . . . . . . . . . . 12
B.3. Array of Signatures . . . . . . . . . . . . . . . . . . . 13
Appendix C. Test Vector Using the ES256 Algorithm . . . . . . . 14
Appendix D. Enhanced JWS Processing Option . . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 15
Document History . . . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
This specification introduces a method for augmenting data expressed
in the JSON [RFC8259] notation, with enveloped signatures, similar to
the scheme used in the XML Signature [XMLDSIG] standard. For
interoperability reasons this specification constrains JSON objects
to the I-JSON [RFC7493] subset.
Show full document text