Signed HTTP Requests (SHREQ)
draft-rundgren-signed-http-requests-01

Document Type Active Internet-Draft (individual)
Last updated 2019-09-09
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                                        A. Rundgren
Internet-Draft                                               Independent
Intended status: Informational                         September 8, 2019
Expires: March 11, 2020

                      Signed HTTP Requests (SHREQ)
                 draft-rundgren-signed-http-requests-01

Abstract

   The SHREQ specification describes how the JSON Web Signature (JWS)
   specification combined with the JSON Canonicalization Scheme (JCS),
   can be utilized to support HTTP based applications needing digitally
   signed requests.  SHREQ is specifically tailored for Web applications
   using JSON as data interchange format.  There is also a SHREQ scheme
   for HTTP requests that do not have a body ("payload") like GET.
   SHREQ was designed to be agnostic with respect to REST concepts
   versus traditional GET/POST schemes.

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 March 11, 2020.

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.  Code Components extracted from this document must

Rundgren                 Expires March 11, 2020                 [Page 1]
Internet-Draft     draft-rundgren-signed-http-requests    September 2019

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  HTTP Processing . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Determining Request Type  . . . . . . . . . . . . . . . .   4
     3.2.  Return Codes  . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Processing of JSON Based Requests . . . . . . . . . . . . . .   5
     4.1.  Request Creation  . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Request Validation  . . . . . . . . . . . . . . . . . . .   8
   5.  Processing of URI Based Requests  . . . . . . . . . . . . . .   9
     5.1.  Request Creation  . . . . . . . . . . . . . . . . . . . .  10
     5.2.  Request Validation  . . . . . . . . . . . . . . . . . . .  11
   6.  Common Operations . . . . . . . . . . . . . . . . . . . . . .  13
     6.1.  Create Signable JSON Data . . . . . . . . . . . . . . . .  13
     6.2.  Create Signable URI Data  . . . . . . . . . . . . . . . .  13
     6.3.  Create HTTP Header Object . . . . . . . . . . . . . . . .  14
     6.4.  Create JWS Protected Header . . . . . . . . . . . . . . .  15
     6.5.  Create JWS String . . . . . . . . . . . . . . . . . . . .  15
     6.6.  Decode JWS String . . . . . . . . . . . . . . . . . . . .  16
     6.7.  Normalize Target URI  . . . . . . . . . . . . . . . . . .  16
     6.8.  Normalize Header Data . . . . . . . . . . . . . . . . . .  17
     6.9.  Validate HTTP Header Object . . . . . . . . . . . . . . .  18
     6.10. Validate JWS Signature  . . . . . . . . . . . . . . . . .  19
     6.11. Time Stamps . . . . . . . . . . . . . . . . . . . . . . .  20
     6.12. Hash Algorithms . . . . . . . . . . . . . . . . . . . . .  20
   7.  Local Naming Conventions  . . . . . . . . . . . . . . . . . .  21
   8.  Attachments . . . . . . . . . . . . . . . . . . . . . . . . .  21
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  22
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  22
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  22
     12.2.  Informal References  . . . . . . . . . . . . . . . . . .  24
   Appendix A.  Test Vectors . . . . . . . . . . . . . . . . . . . .  24
     A.1.  Type=URI, Method=GET, Algorithm=HS256 . . . . . . . . . .  24
     A.2.  Type=JSON, Method=POST, Algorithm=ES256 . . . . . . . . .  25
Show full document text