Signing HTTP Messages
draft-ietf-httpbis-message-signatures-03
HTTP A. Backman, Ed.
Internet-Draft Amazon
Intended status: Standards Track J. Richer
Expires: 9 October 2021 Bespoke Engineering
M. Sporny
Digital Bazaar
7 April 2021
Signing HTTP Messages
draft-ietf-httpbis-message-signatures-03
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 to Readers
_RFC EDITOR: please remove this section before publication_
Discussion of this draft takes place on the HTTP working group
mailing list (ietf-http-wg@w3.org), which is archived at
https://lists.w3.org/Archives/Public/ietf-http-wg/
(https://lists.w3.org/Archives/Public/ietf-http-wg/).
Working Group information can be found at https://httpwg.org/
(https://httpwg.org/); source code and issues list for this draft can
be found at https://github.com/httpwg/http-extensions/labels/
signatures (https://github.com/httpwg/http-extensions/labels/
signatures).
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/.
Backman, et al. Expires 9 October 2021 [Page 1]
Internet-Draft Signing HTTP Messages April 2021
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 9 October 2021.
Copyright Notice
Copyright (c) 2021 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
1.5. Application of HTTP Message Signatures . . . . . . . . . 7
2. HTTP Message Signature Covered Content . . . . . . . . . . . 8
2.1. HTTP Headers . . . . . . . . . . . . . . . . . . . . . . 9
2.1.1. Canonicalized Structured HTTP Headers . . . . . . . . 9
2.1.2. Canonicalization Examples . . . . . . . . . . . . . . 9
2.2. Dictionary Structured Field Members . . . . . . . . . . . 10
2.2.1. Canonicalization Examples . . . . . . . . . . . . . . 10
2.3. List Prefixes . . . . . . . . . . . . . . . . . . . . . . 11
2.3.1. Canonicalization Examples . . . . . . . . . . . . . . 11
2.4. Specialty Content Fields . . . . . . . . . . . . . . . . 12
2.4.1. Request Target . . . . . . . . . . . . . . . . . . . 12
2.4.2. Signature Parameters . . . . . . . . . . . . . . . . 13
2.5. Creating the Signature Input String . . . . . . . . . . . 16
3. HTTP Message Signatures . . . . . . . . . . . . . . . . . . . 17
3.1. Creating a Signature . . . . . . . . . . . . . . . . . . 18
3.2. Verifying a Signature . . . . . . . . . . . . . . . . . . 20
3.2.1. Enforcing Application Requirements . . . . . . . . . 21
3.3. Signature Algorithm Methods . . . . . . . . . . . . . . . 22
3.3.1. RSASSA-PSS using SHA-512 . . . . . . . . . . . . . . 22
3.3.2. RSASSA-PKCS1-v1_5 using SHA-256 . . . . . . . . . . . 22
Show full document text