OAuth Dynamic Client Registration Protocol
draft-ietf-oauth-dyn-reg-00

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2012-05-23
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                   T. Hardjono, Ed.
Internet-Draft                                                       MIT
Intended status: Standards Track                             M. Machulak
Expires: November 24, 2012                          Newcastle University
                                                                E. Maler
                                                             XMLgrrl.com
                                                               C. Scholz
                                                         COM.lounge GmbH
                                                            May 23, 2012

               OAuth Dynamic Client Registration Protocol
                      draft-ietf-oauth-dyn-reg-00

Abstract

   This specification proposes an OAuth Dynamic Client Registration
   protocol.

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 November 24, 2012.

Copyright Notice

   Copyright (c) 2012 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, et al.        Expires November 24, 2012               [Page 1]
Internet-Draft      OAuth Dynamic Client Registration           May 2012

   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.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  The client needs to be uniquely identifiable by the
           authorization server . . . . . . . . . . . . . . . . . . .  5
     3.2.  The authorization server must collect metadata about a
           client for later user interaction  . . . . . . . . . . . .  5
     3.3.  The authorization server must have the option of
           strongly authenticating the client and its metadata  . . .  5
     3.4.  Dynamic client registration must be possible from both
           web-server applications and applications with other
           capabilities and limitations, such as native
           applications . . . . . . . . . . . . . . . . . . . . . . .  6
     3.5.  Transaction integrity must be ensured in large
           deployments where data propagation can be an issue . . . .  6
     3.6.  Use of standardized discovery protocol . . . . . . . . . .  6
     3.7.  UMA design principles and requirements . . . . . . . . . .  7
   4.  Analysis of Registration Flow Options  . . . . . . . . . . . .  7
   5.  Client Registration with Pushed Metadata . . . . . . . . . . .  8
     5.1.  Client Registration Request  . . . . . . . . . . . . . . .  9
     5.2.  Client Registration Response . . . . . . . . . . . . . . . 10
     5.3.  Error Response . . . . . . . . . . . . . . . . . . . . . . 11
   6.  Client Registration with Pushed URL and Pulled Metadata  . . . 12
     6.1.  Client Registration Request  . . . . . . . . . . . . . . . 13
     6.2.  Client Discovery . . . . . . . . . . . . . . . . . . . . . 13
     6.3.  Client Registration Response . . . . . . . . . . . . . . . 13
     6.4.  Error Response . . . . . . . . . . . . . . . . . . . . . . 14
   7.  Native Application Client Registration . . . . . . . . . . . . 15
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   9.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 17
   10. Document History . . . . . . . . . . . . . . . . . . . . . . . 17
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text