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

The information below is for an old version of the document
Document Type Active Internet-Draft (oauth WG)
Last updated 2012-11-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)
Network Working Group                                     J. Richer, Ed.
Internet-Draft                                     The MITRE Corporation
Intended status: Standards Track                             T. Hardjono
Expires: May 9, 2013                                                 MIT
                                                             M. Machulak
                                                    Newcastle University
                                                                E. Maler
                                                             XMLgrrl.com
                                                               C. Scholz
                                                         COM.lounge GmbH
                                                             N. Sakimura
                                                                     NRI
                                                              J. Bradley
                                                           Ping Identity
                                                                M. Jones
                                                               Microsoft
                                                        November 5, 2012

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

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 May 9, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

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

   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
   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
     1.3.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  4
       1.3.1.  The client needs to be uniquely identifiable by
               the authorization server . . . . . . . . . . . . . . .  4
       1.3.2.  The authorization server must collect metadata
               about a client for later user interaction  . . . . . .  4
       1.3.3.  The authorization server should have the option of
               strongly authenticating the client and its metadata  .  4
       1.3.4.  Dynamic client registration must be possible from
               both web-server applications and applications with
               other capabilities and limitations, such as native
               applications . . . . . . . . . . . . . . . . . . . . .  4
       1.3.5.  Transaction integrity must be ensured  . . . . . . . .  5
   2.  Client Registration Endpoint . . . . . . . . . . . . . . . . .  5
     2.1.  Client Association Request . . . . . . . . . . . . . . . .  6
     2.2.  Client Association Response  . . . . . . . . . . . . . . .  8
     2.3.  Client Update Request  . . . . . . . . . . . . . . . . . .  9
     2.4.  Client Update Response . . . . . . . . . . . . . . . . . . 10
     2.5.  Rotate Secret Request  . . . . . . . . . . . . . . . . . . 11
     2.6.  Rotate Secret Response . . . . . . . . . . . . . . . . . . 11
     2.7.  Client Registration Error Response . . . . . . . . . . . . 12
   3.  Client Metadata  . . . . . . . . . . . . . . . . . . . . . . . 13
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 16
   7.  Document History . . . . . . . . . . . . . . . . . . . . . . . 16
Show full document text