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

Document Type Active Internet-Draft (individual)
Last updated 2017-01-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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: July 14, 2017                                    Digital Bazaar
                                                        January 10, 2017

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

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

   This specification is a part of the Web Payments [1] work.  Feedback
   related to this specification should be sent to public-
   webpayments@w3.org [2].

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 http://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 July 14, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Cavage & Sporny           Expires July 14, 2017                 [Page 1]
Internet-Draft            Signing HTTP Messages             January 2017

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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 . . . . . . . . . . . .   3
     1.2.  Using Signatures in HTTP Responses  . . . . . . . . . . .   4
   2.  The Components of a Signature . . . . . . . . . . . . . . . .   4
     2.1.  Signature Parameters  . . . . . . . . . . . . . . . . . .   4
       2.1.1.  keyId . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.2.  algorithm . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.3.  headers . . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.4.  signature . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Ambiguous Parameters  . . . . . . . . . . . . . . . . . .   5
     2.3.  Signature String Construction . . . . . . . . . . . . . .   5
     2.4.  Creating a Signature  . . . . . . . . . . . . . . . . . .   6
     2.5.  Verifying a Signature . . . . . . . . . . . . . . . . . .   7
   3.  The 'Signature' HTTP Authentication Scheme  . . . . . . . . .   7
     3.1.  Authorization Header  . . . . . . . . . . . . . . . . . .   7
       3.1.1.  Initiating Signature Authorization  . . . . . . . . .   8
       3.1.2.  RSA Example . . . . . . . . . . . . . . . . . . . . .   8
       3.1.3.  HMAC Example  . . . . . . . . . . . . . . . . . . . .   9
   4.  The 'Signature' HTTP Header . . . . . . . . . . . . . . . . .   9
     4.1.  Signature Header  . . . . . . . . . . . . . . . . . . . .  10
       4.1.1.  RSA Example . . . . . . . . . . . . . . . . . . . . .  10
       4.1.2.  HMAC Example  . . . . . . . . . . . . . . . . . . . .  11
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     5.2.  Informative References  . . . . . . . . . . . . . . . . .  12
     5.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix A.  Security Considerations  . . . . . . . . . . . . . .  13
   Appendix B.  Extensions . . . . . . . . . . . . . . . . . . . . .  13
   Appendix C.  Test Values  . . . . . . . . . . . . . . . . . . . .  14
     C.1.  Default Test  . . . . . . . . . . . . . . . . . . . . . .  14
     C.2.  Basic Test  . . . . . . . . . . . . . . . . . . . . . . .  15
     C.3.  All Headers Test  . . . . . . . . . . . . . . . . . . . .  15
   Appendix D.  Acknowledgements . . . . . . . . . . . . . . . . . .  16
Show full document text