Signing HTTP Messages
draft-cavage-http-signatures-11

Document Type Active Internet-Draft (individual)
Last updated 2019-04-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          M. Cavage
Internet-Draft                                                    Oracle
Intended status: Standards Track                               M. Sporny
Expires: October 26, 2019                                 Digital Bazaar
                                                          April 24, 2019

                         Signing HTTP Messages
                    draft-cavage-http-signatures-11

Abstract

   When communicating over the Internet using the HTTP protocol, it can
   be desirable for a server or client to authenticate the sender of a
   particular message.  It can also be desirable to ensure that the
   message was not tampered with during transit.  This document
   describes a way for servers and clients to simultaneously add
   authentication and message integrity to HTTP messages by using a
   digital signature.

Feedback

   WARNING: DO NOT IMPLEMENT THIS SPECIFICATION AND PUSH THE CODE INTO
   PRODUCTION.  THIS VERSION OF THE SPECIFICATION IS ONLY FOR
   EXPERIMENTAL IMPLEMENTATIONS.

   This version (draft-cavage-http-signatures-11) is experimental and
   implementers should be aware that a number of new features have been
   introduced in this version that change previous algorithms in subtle
   but important ways.  Namely, there is now a backwards-compatible way
   to modify the signature string construction algorithm, as well as two
   new Signature Parameters to enable web browser-based clients to
   include a signature creation and expiration timestamp.  The new
   features are designed to be fully backwards compatible.  Older
   features have been deprecated, but are still supported in the
   algorithms described by this specification.  There are no plans to
   remove deprecated features from the specification to ensure backwards
   compatability for implementations dating back to 2013.  Test vectors
   still need to be added for the new algorithms and digital signature
   types such as Ed25519.

   This specification is a joint work product of the W3C Digital
   Verification Community Group [1] and the W3C Credentials Community
   Group [2].  Feedback related to this specification should logged in
   the issue tracker [3] or be sent to public-credentials@w3.org [4].

Cavage & Sporny         Expires October 26, 2019                [Page 1]
Internet-Draft            Signing HTTP Messages               April 2019

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 October 26, 2019.

Copyright Notice

   Copyright (c) 2019 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Using Signatures in HTTP Requests . . . . . . . . . . . .   4
     1.2.  Using Signatures in HTTP Responses  . . . . . . . . . . .   5
   2.  The Components of a Signature . . . . . . . . . . . . . . . .   5
     2.1.  Signature Parameters  . . . . . . . . . . . . . . . . . .   5
       2.1.1.  keyId . . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.2.  signature . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.3.  algorithm . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.4.  created . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.5.  expires . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.6.  headers . . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Ambiguous Parameters  . . . . . . . . . . . . . . . . . .   7
     2.3.  Signature String Construction . . . . . . . . . . . . . .   7
     2.4.  Creating a Signature  . . . . . . . . . . . . . . . . . .   9
     2.5.  Verifying a Signature . . . . . . . . . . . . . . . . . .  10
   3.  The 'Signature' HTTP Authentication Scheme  . . . . . . . . .  10
     3.1.  Authorization Header  . . . . . . . . . . . . . . . . . .  10

Cavage & Sporny         Expires October 26, 2019                [Page 2]
Internet-Draft            Signing HTTP Messages               April 2019
Show full document text