A Framework For Decentralized Bearer Token Issuance in HTTP
draft-thornburgh-fwk-dc-token-iss-01

Document Type Active Internet-Draft (individual)
Author Michael Thornburgh 
Last updated 2020-08-26
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) 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)
Independent Submission                                     M. Thornburgh
Internet-Draft                                            26 August 2020
Intended status: Experimental                                           
Expires: 27 February 2021

      A Framework For Decentralized Bearer Token Issuance in HTTP
                  draft-thornburgh-fwk-dc-token-iss-01

Abstract

   This memo describes a protocol framework for HTTP clients to obtain
   bearer tokens for accessing restricted resources, where in some
   applications the client may not have prior knowledge of, or a direct
   relationship with, the resource server's authorization infrastructure
   (such as in decentralized identity systems).  Semi-concrete
   applications of the framework using proof-of-possession and TLS
   client certificate mechanisms are also described.

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 27 February 2021.

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.

Thornburgh              Expires 27 February 2021                [Page 1]
Internet-Draft        Decentralized Token Issuance           August 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
       1.1.1.  Use Cases . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  General Framework . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Nonce Considerations  . . . . . . . . . . . . . . . . . .   6
     2.2.  Common Token Response . . . . . . . . . . . . . . . . . .   6
     2.3.  Common Mechanism Flow . . . . . . . . . . . . . . . . . .   7
   3.  Proof-of-Possession Mechanism . . . . . . . . . . . . . . . .   8
     3.1.  Proof Token . . . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Proof-of-Possession API . . . . . . . . . . . . . . . . .   9
     3.3.  Proof-of-Possession Example . . . . . . . . . . . . . . .  10
   4.  TLS Client Certificate Mechanism  . . . . . . . . . . . . . .  12
     4.1.  Client Certificate API  . . . . . . . . . . . . . . . . .  13
     4.2.  Client Certificate Example  . . . . . . . . . . . . . . .  14
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  17
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   This memo describes a general protocol framework for HTTP clients to
   obtain bearer tokens (Section 1.2 of [RFC6750]) from a resource
   server's authorization service in order to access protected resources
   on the server.  This framework is especially intended for systems
   (such as decentralized identity systems like [WebID], and
   decentralized social or mashup data systems like the Solid project
   (https://solidproject.org)) where the client might not have prior
   knowledge of, or a preexisting direct relationship with, the
   authorization service for the resource server; however, it can be
   applied in other use cases as well.

   The protocol includes a method for the client to discover the
   nature(s) of principals (such as identities, capabilities, sender-
   constrained access tokens, or verifiable credentials) that the server
   expects to interact with, and methods for the client to discover the
   API endpoint URIs for multiple potential mechanisms for obtaining
   bearer tokens.  The framework is constructed to mitigate man-in-the-
   middle token-stealing attacks.

   This memo defines two mechanisms within the framework for a client to
   obtain a bearer token: one using a cryptographic proof-of-possession,
Show full document text