Signing HTTP Messages
draft-ietf-httpbis-message-signatures-00
HTTPbis Working Group A. Backman, Ed.
Internet-Draft Amazon
Intended status: Standards Track J. Richer
Expires: 12 October 2020 Bespoke Engineering
M. Sporny
Digital Bazaar
10 April 2020
Signing HTTP Messages
draft-ietf-httpbis-message-signatures-00
Abstract
This document describes a mechanism for creating, encoding, and
verifying digital signatures or message authentication codes over
content within an HTTP message. This mechanism supports use cases
where the full HTTP message may not be known to the signer, and where
the message may be transformed (e.g., by intermediaries) before
reaching the verifier.
Note
This draft is based on draft-cavage-http-signatures-12. The
community (https://github.com/w3c-dvcg/http-signatures/
issues?page=2&q=is%3Aissue+is%3Aopen) and the authors have identified
several issues with the current text. Additionally, the authors have
identified a number of features that are required in order to support
additional use cases. In order to preserve continuity with the
effort that has been put into draft-cavage-http-signatures-12, this
draft maintains normative compatibility with it, and thus does not
address these issues or include these features, as doing so requires
making backwards-incompatible changes to normative requirements.
While such changes are inevitable, the editor recommends that they be
driven by working group discussion following adoption of the draft
(see Topics for Working Group Discussion). The editor requests that
the working group recognize the intent of this initial draft and this
recommendation when considering adoption of this draft.
This note is to be removed before publishing as an RFC.
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
Backman, et al. Expires 12 October 2020 [Page 1]
Internet-Draft Signing HTTP Messages April 2020
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 12 October 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
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. Code Components
extracted from this document must include Simplified BSD License text
as described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Discussion . . . . . . . . . . . . . . . . . 4
1.2. HTTP Message Transformations . . . . . . . . . . . . . . 5
1.3. Safe Transformations . . . . . . . . . . . . . . . . . . 5
1.4. Conventions and Terminology . . . . . . . . . . . . . . . 6
2. Identifying and Canonicalizing Content . . . . . . . . . . . 7
2.1. HTTP Header Fields . . . . . . . . . . . . . . . . . . . 7
2.2. Signature Creation Time . . . . . . . . . . . . . . . . . 8
2.3. Signature Expiration Time . . . . . . . . . . . . . . . . 9
2.4. Target Endpoint . . . . . . . . . . . . . . . . . . . . . 9
3. HTTP Message Signatures . . . . . . . . . . . . . . . . . . . 10
3.1. Signature Metadata . . . . . . . . . . . . . . . . . . . 10
3.2. Creating a Signature . . . . . . . . . . . . . . . . . . 11
3.2.1. Choose and Set Signature Metadata Properties . . . . 11
3.2.2. Create the Signature Input . . . . . . . . . . . . . 13
3.2.3. Sign the Signature Input . . . . . . . . . . . . . . 14
3.3. Verifying a Signature . . . . . . . . . . . . . . . . . . 14
3.3.1. Enforcing Application Requirements . . . . . . . . . 15
Show full document text