Grant Negotiation and Authorization Protocol
draft-ietf-gnap-core-protocol-02

Document Type Active Internet-Draft (gnap WG)
Authors Justin Richer  , Aaron Parecki  , Fabien Imbault 
Last updated 2020-11-17
Replaces draft-richer-transactional-authz
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Additional Resources
- GitHub Repository
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
GNAP                                                      J. Richer, Ed.
Internet-Draft                                       Bespoke Engineering
Intended status: Standards Track                              A. Parecki
Expires: 21 May 2021                                                Okta
                                                              F. Imbault
                                                                acert.io
                                                        17 November 2020

              Grant Negotiation and Authorization Protocol
                    draft-ietf-gnap-core-protocol-02

Abstract

   This document defines a mechanism for delegating authorization to a
   piece of software, and conveying that delegation to the software.
   This delegation can include access to a set of APIs as well as
   information passed directly to the software.

   This document has been prepared by the GNAP working group design team
   of Kathleen Moriarty, Fabien Imbault, Dick Hardt, Mike Jones, and
   Justin Richer.  This document is intended as a starting point for the
   working group and includes decision points for discussion and
   agreement.  Many of the features in this proposed protocol can be
   accomplished in a number of ways.  Where possible, the editor has
   included notes and discussion from the design team regarding the
   options as understood.

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 21 May 2021.

Richer, et al.             Expires 21 May 2021                  [Page 1]
Internet-Draft  Grant Negotiation and Authorization Prot   November 2020

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.  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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
     1.2.  Roles . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Elements  . . . . . . . . . . . . . . . . . . . . . . . .   6
     1.4.  Sequences . . . . . . . . . . . . . . . . . . . . . . . .   7
       1.4.1.  Redirect-based Interaction  . . . . . . . . . . . . .  10
       1.4.2.  User-code Interaction . . . . . . . . . . . . . . . .  12
       1.4.3.  Asynchronous Authorization  . . . . . . . . . . . . .  14
       1.4.4.  Software-only Authorization . . . . . . . . . . . . .  15
       1.4.5.  Refreshing an Expired Access Token  . . . . . . . . .  16
   2.  Requesting Access . . . . . . . . . . . . . . . . . . . . . .  17
     2.1.  Requesting Resources  . . . . . . . . . . . . . . . . . .  19
       2.1.1.  Requesting a Single Access Token  . . . . . . . . . .  19
       2.1.2.  Requesting Resources By Reference . . . . . . . . . .  21
       2.1.3.  Requesting Multiple Access Tokens . . . . . . . . . .  23
       2.1.4.  Signaling Token Behavior  . . . . . . . . . . . . . .  25
     2.2.  Requesting User Information . . . . . . . . . . . . . . .  26
     2.3.  Identifying the RC  . . . . . . . . . . . . . . . . . . .  27
       2.3.1.  Identifying the RC Instance . . . . . . . . . . . . .  29
       2.3.2.  Identifying the RC Key  . . . . . . . . . . . . . . .  30
       2.3.3.  Providing Displayable RC Information  . . . . . . . .  31
       2.3.4.  Authenticating the RC . . . . . . . . . . . . . . . .  31
     2.4.  Identifying the User  . . . . . . . . . . . . . . . . . .  32
       2.4.1.  Identifying the User by Reference . . . . . . . . . .  33
     2.5.  Interacting with the User . . . . . . . . . . . . . . . .  33
       2.5.1.  Redirect to an Arbitrary URL  . . . . . . . . . . . .  35
       2.5.2.  Open an Application-specific URL  . . . . . . . . . .  36
       2.5.3.  Receive a Callback After Interaction  . . . . . . . .  36
Show full document text