Transactional Authorization
draft-richer-transactional-authz-02

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
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                                     J. Richer, Ed.
Internet-Draft                                       Bespoke Engineering
Intended status: Standards Track                            July 8, 2019
Expires: January 9, 2020

                      Transactional Authorization
                  draft-richer-transactional-authz-02

Abstract

   This document defines a mechanism for delegating authorization to a
   piece of software, and conveying that delegation to the software.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 RFC 2119 [RFC2119] RFC 8174 [RFC8174] when, and only when, they
   appear in all capitals, as shown here.

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 January 9, 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

Richer                   Expires January 9, 2020                [Page 1]
Internet-Draft             transactional-authz                 July 2019

   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.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Parties . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Sequence  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Transaction request . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Client  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Resource  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  User  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Interact  . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.5.  Keys  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Interaction response  . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Redirect interaction  . . . . . . . . . . . . . . . . . .   8
     3.2.  Callback response . . . . . . . . . . . . . . . . . . . .   9
     3.3.  Secondary device interaction  . . . . . . . . . . . . . .   9
   4.  Wait response . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  Interaction at the AS . . . . . . . . . . . . . . . . . . . .  11
   6.  Error response  . . . . . . . . . . . . . . . . . . . . . . .  12
   7.  Transaction continue request  . . . . . . . . . . . . . . . .  12
   8.  Token response  . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Presenting Tokens to the RS . . . . . . . . . . . . . . .  13
   9.  Handle references . . . . . . . . . . . . . . . . . . . . . .  13
     9.1.  Presenting handles  . . . . . . . . . . . . . . . . . . .  14
     9.2.  Validating handles  . . . . . . . . . . . . . . . . . . .  14
     9.3.  Transaction handles . . . . . . . . . . . . . . . . . . .  14
     9.4.  Client handles  . . . . . . . . . . . . . . . . . . . . .  15
     9.5.  Resource handles  . . . . . . . . . . . . . . . . . . . .  15
       9.5.1.  Resource-first  . . . . . . . . . . . . . . . . . . .  16
     9.6.  User handles  . . . . . . . . . . . . . . . . . . . . . .  17
     9.7.  Key handles . . . . . . . . . . . . . . . . . . . . . . .  17
   10. Binding Keys  . . . . . . . . . . . . . . . . . . . . . . . .  18
     10.1.  Binding a key to a transaction . . . . . . . . . . . . .  18
     10.2.  Detached JWS . . . . . . . . . . . . . . . . . . . . . .  19
     10.3.  Mutual TLS . . . . . . . . . . . . . . . . . . . . . . .  19
     10.4.  Validating DID . . . . . . . . . . . . . . . . . . . . .  19
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
Show full document text