Federated Authorization for User-Managed Access (UMA) 2.0
draft-maler-oauth-umafedauthz-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

       Federated Authorization for User-Managed Access (UMA) 2.0
                    draft-maler-oauth-umafedauthz-00

Abstract

   This specification defines a means for an UMA-enabled authorization
   server and resource server to be loosely coupled, or federated, in a
   secure and authorized resource owner context.

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

Maler, et al.            Expires August 17, 2019                [Page 1]
Internet-Draft                                             February 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
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
     1.2.  Abstract Flow . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  HTTP Usage, API Security, and Identity Context  . . . . .   5
     1.4.  Separation of Responsibility and Authority  . . . . . . .   6
     1.5.  Protection API Summary  . . . . . . . . . . . . . . . . .   7
       1.5.1.  Permissions . . . . . . . . . . . . . . . . . . . . .   8
   2.  Authorization Server Metadata . . . . . . . . . . . . . . . .   8
   3.  Resource Registration Endpoint  . . . . . . . . . . . . . . .   9
     3.1.  Resource Description  . . . . . . . . . . . . . . . . . .  11
       3.1.1.  Scope Description . . . . . . . . . . . . . . . . . .  12
     3.2.  Resource Registration API . . . . . . . . . . . . . . . .  13
       3.2.1.  Create Resource Description . . . . . . . . . . . . .  14
       3.2.2.  Read Resource Description . . . . . . . . . . . . . .  15
       3.2.3.  Update Resource Description . . . . . . . . . . . . .  16
       3.2.4.  Delete Resource Description . . . . . . . . . . . . .  17
       3.2.5.  List Resource Descriptions  . . . . . . . . . . . . .  17
   4.  Permission Endpoint . . . . . . . . . . . . . . . . . . . . .  18
     4.1.  Resource Server Request to Permission Endpoint  . . . . .  20
     4.2.  Authorization Server Response to Resource Server on
           Permission Request Success  . . . . . . . . . . . . . . .  22
     4.3.  Authorization Server Response to Resource Server on
           Permission Request Failure  . . . . . . . . . . . . . . .  23
   5.  Token Introspection Endpoint  . . . . . . . . . . . . . . . .  23
     5.1.  Resource Server Request to Token Introspection Endpoint .  24
       5.1.1.  Authorization Server Response to Resource Server on
               Token Introspection Success . . . . . . . . . . . . .  25
   6.  Error Messages  . . . . . . . . . . . . . . . . . . . . . . .  26
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  27
   8.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  27
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  28
     9.1.  OAuth 2.0 Authorization Server Metadata Registry  . . . .  28
       9.1.1.  Registry Contents . . . . . . . . . . . . . . . . . .  28
     9.2.  OAuth Token Introspection Response Registration . . . . .  28
Show full document text