datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

User-Managed Access (UMA) Profile of OAuth 2.0
draft-hardjono-oauth-umacore-10

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-07-21
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                   T. Hardjono, Ed.
Internet-Draft                                                       MIT
Intended status: Standards Track                           July 20, 2014
Expires: January 21, 2015

             User-Managed Access (UMA) Profile of OAuth 2.0
                    draft-hardjono-oauth-umacore-10

Abstract

   User-Managed Access (UMA) is a profile of OAuth 2.0.  UMA defines how
   resource owners can control protected-resource access by clients
   operated by arbitrary requesting parties, where the resources reside
   on any number of resource servers, and where a centralized
   authorization server governs access based on resource owner policy.
   This revision of the specification is part of UMA V0.9.

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 http://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 21, 2015.

Copyright Notice

   Copyright (c) 2014 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
   (http://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

Hardjono                Expires January 21, 2015                [Page 1]
Internet-Draft                  UMA Core                       July 2014

   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  . . . . . . . . . . . . . . . . .   5
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   5
     1.3.  Achieving Distributed Protection Through APIs and Tokens    7
       1.3.1.  Protection API  . . . . . . . . . . . . . . . . . . .   7
       1.3.2.  Authorization API . . . . . . . . . . . . . . . . . .   8
       1.3.3.  Protected Resource Interface  . . . . . . . . . . . .   9
       1.3.4.  Time-to-Live Considerations . . . . . . . . . . . . .   9
     1.4.  Authorization Server Configuration Data . . . . . . . . .  10
   2.  Protecting a Resource . . . . . . . . . . . . . . . . . . . .  13
   3.  Getting Authorization and Accessing a Resource  . . . . . . .  14
     3.1.  Client Attempts to Access Protected Resource  . . . . . .  16
       3.1.1.  Client Presents No RPT  . . . . . . . . . . . . . . .  16
       3.1.2.  Client Presents RPT . . . . . . . . . . . . . . . . .  16
     3.2.  Resource Server Registers Requested Permission With
           Authorization Server  . . . . . . . . . . . . . . . . . .  18
     3.3.  Resource Server Determines RPT's Status . . . . . . . . .  20
       3.3.1.  Token Introspection . . . . . . . . . . . . . . . . .  20
       3.3.2.  RPT Profile: Bearer . . . . . . . . . . . . . . . . .  20
     3.4.  Client Seeks Authorization for Access . . . . . . . . . .  22
       3.4.1.  Client Obtains RPT  . . . . . . . . . . . . . . . . .  23
       3.4.2.  Client Asks for Authorization Data  . . . . . . . . .  23
     3.5.  Claims-Gathering Flows  . . . . . . . . . . . . . . . . .  26
   4.  Error Messages  . . . . . . . . . . . . . . . . . . . . . . .  26
     4.1.  OAuth Error Responses . . . . . . . . . . . . . . . . . .  27
     4.2.  UMA Error Responses . . . . . . . . . . . . . . . . . . .  27
   5.  Profiles for API Extensibility  . . . . . . . . . . . . . . .  28
     5.1.  Protection API Extensibility Profile  . . . . . . . . . .  29
     5.2.  Authorization API Extensibility Profile . . . . . . . . .  30
     5.3.  Resource Interface Extensibility Profile  . . . . . . . .  31
   6.  Specifying Additional Profiles  . . . . . . . . . . . . . . .  32
     6.1.  Specifying Profiles of UMA  . . . . . . . . . . . . . . .  33
     6.2.  Specifying RPT Profiles . . . . . . . . . . . . . . . . .  33
     6.3.  Specifying Claim Profiles . . . . . . . . . . . . . . . .  34

[include full document text]