User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization
draft-maler-oauth-umagrant-00

Document Type Active Internet-Draft (individual)
Last updated 2019-02-13
Stream (None)
Intended RFC status (None)
Formats plain text 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                                      E. Maler, Ed.
Internet-Draft                                                 ForgeRock
Intended status: Informational                               M. Machulak
Expires: August 17, 2019                                            HSBC
                                                               J. Richer
                                                     Bespoke Engineering
                                                             T. Hardjono
                                                                     MIT
                                                       February 13, 2019

    User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization
                     draft-maler-oauth-umagrant-00

Abstract

   This specification defines a means for a client, representing a
   requesting party, to use a permission ticket to request an OAuth 2.0
   access token to gain access to a protected resource asynchronously
   from the time a resource owner authorizes access.

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 August 17, 2019.

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

Maler, et al.            Expires August 17, 2019                [Page 1]
Internet-Draft                                             February 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
     1.2.  Roles . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Abstract Flow . . . . . . . . . . . . . . . . . . . . . .   5
       1.3.1.  Authorization Process . . . . . . . . . . . . . . . .   7
   2.  Authorization Server Metadata . . . . . . . . . . . . . . . .   8
   3.  Flow Details  . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Client Requests Resource Without Providing an Access
           Token . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.2.  Resource Server Responds to Client's Tokenless Access
           Attempt . . . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  Resource Server Response to Client on Permission
               Request Success . . . . . . . . . . . . . . . . . . .  10
       3.2.2.  Resource Server Response to Client on Permission
               Request Failure . . . . . . . . . . . . . . . . . . .  10
     3.3.  Client Seeks RPT on Requesting Party's Behalf . . . . . .  11
       3.3.1.  Client Request to Authorization Server for RPT  . . .  11
       3.3.2.  Client Redirect of Requesting Party to Authorization
               Server for Interactive Claims-Gathering . . . . . . .  13
       3.3.3.  Authorization Server Redirect of Requesting Party
               Back to Client After Interactive Claims-Gathering . .  15
       3.3.4.  Authorization Assessment and Results Determination  .  16
       3.3.5.  Authorization Server Response to Client on
               Authorization Success . . . . . . . . . . . . . . . .  18
       3.3.6.  Authorization Server Response to Client on
               Authorization Failure . . . . . . . . . . . . . . . .  20
     3.4.  Client Requests Resource and Provides an RPT  . . . . . .  23
     3.5.  Resource Server Responds to Client's RPT-Accompanied
           Resource Request  . . . . . . . . . . . . . . . . . . . .  23
     3.6.  Authorization Server Refreshes RPT  . . . . . . . . . . .  24
     3.7.  Client Requests Token Revocation  . . . . . . . . . . . .  24
   4.  Profiles and Extensions . . . . . . . . . . . . . . . . . . .  24
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  25
     5.1.  Cross-Site Request Forgery  . . . . . . . . . . . . . . .  25
Show full document text