OAuth 2.0 Dynamic Client Registration Protocol
draft-ietf-oauth-dyn-reg-10

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2013-05-05
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)
OAuth Working Group                                       J. Richer, Ed.
Internet-Draft                                     The MITRE Corporation
Intended status: Standards Track                              J. Bradley
Expires: November 06, 2013                                 Ping Identity
                                                              M.B. Jones
                                                               Microsoft
                                                             M. Machulak
                                                    Newcastle University
                                                            May 05, 2013

             OAuth 2.0 Dynamic Client Registration Protocol
                      draft-ietf-oauth-dyn-reg-10

Abstract

   This specification defines an endpoint and protocol for dynamic
   registration of OAuth 2.0 Clients at an Authorization Server and
   methods for the dynamically registered client to manage its
   registration.

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 06, 2013.

Copyright Notice

   Copyright (c) 2013 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

Richer, et al.         Expires November 06, 2013                [Page 1]
Internet-Draft               oauth-dyn-reg                      May 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Client Metadata . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Relationship Between Grant Types and Response Types . . .   7
     2.2.  Human Readable Client Metadata  . . . . . . . . . . . . .   8
   3.  Client Registration Endpoint  . . . . . . . . . . . . . . . .   9
     3.1.  Client Registration Request . . . . . . . . . . . . . . .  10
     3.2.  Client Registration Response  . . . . . . . . . . . . . .  11
   4.  Client Configuration Endpoint . . . . . . . . . . . . . . . .  11
     4.1.  Forming the Client Configuration Endpoint URL . . . . . .  12
     4.2.  Client Read Request . . . . . . . . . . . . . . . . . . .  12
     4.3.  Client Update Request . . . . . . . . . . . . . . . . . .  13
     4.4.  Client Delete Request . . . . . . . . . . . . . . . . . .  14
   5.  Responses . . . . . . . . . . . . . . . . . . . . . . . . . .  15
     5.1.  Client Information Response . . . . . . . . . . . . . . .  15
     5.2.  Client Registration Error Response  . . . . . . . . . . .  17
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  20
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  21
   Appendix B.  Document History . . . . . . . . . . . . . . . . . .  21
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  24

1.  Introduction

   In some use-case scenarios, it is desirable or necessary to allow
   OAuth 2.0 clients to obtain authorization from an OAuth 2.0
   authorization server without requiring the two parties to interact
   beforehand.  Nevertheless, in order for the authorization server to
   accurately and securely represent to end-users which client is
   seeking authorization to access the end-user's resources, a method
   for automatic and unique registration of clients is needed.  The
   OAuth 2.0 authorization framework does not define how the
   relationship between the Client and the Authorization Server is
   initialized, or how a given client is assigned a unique Client
   Identifier.  Historically, this has happened out-of-band from the
Show full document text