OAuth 2.0 Dynamic Client Registration Protocol
draft-ietf-oauth-dyn-reg-28
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (oauth WG) | |
Last updated | 2015-04-21 | ||
Replaces | draft-richer-oauth-dyn-reg-core | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | plain text pdf html bibtex | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Hannes Tschofenig | ||
Shepherd write-up | Show (last changed 2015-03-02) | ||
IESG | IESG state | IESG Evaluation::AD Followup | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs a YES. Needs 5 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Kathleen Moriarty | ||
Send notices to | oauth-chairs@ietf.org, draft-ietf-oauth-dyn-reg@ietf.org | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | None |
OAuth Working Group J. Richer, Ed. Internet-Draft Intended status: Standards Track M. Jones Expires: October 23, 2015 Microsoft J. Bradley Ping Identity M. Machulak Newcastle University P. Hunt Oracle Corporation April 21, 2015 OAuth 2.0 Dynamic Client Registration Protocol draft-ietf-oauth-dyn-reg-28 Abstract This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during 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 October 23, 2015. Richer, et al. Expires October 23, 2015 [Page 1] Internet-Draft OAuth 2.0 Dynamic Registration April 2015 Copyright Notice Copyright (c) 2015 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 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 . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Protocol Flow . . . . . . . . . . . . . . . . . . . . . . 5 2. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 6 2.1. Relationship between Grant Types and Response Types . . . 11 2.2. Human-Readable Client Metadata . . . . . . . . . . . . . 11 2.3. Software Statement . . . . . . . . . . . . . . . . . . . 12 3. Client Registration Endpoint . . . . . . . . . . . . . . . . 14 3.1. Client Registration Request . . . . . . . . . . . . . . . 14 3.1.1. Client Registration Request Using a Software Statement . . . . . . . . . . . . . . . . . . . . . . 16 3.2. Responses . . . . . . . . . . . . . . . . . . . . . . . . 17 3.2.1. Client Information Response . . . . . . . . . . . . . 17 3.2.2. Client Registration Error Response . . . . . . . . . 19 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 4.1. OAuth Dynamic Client Registration Metadata Registry . . . 21 4.1.1. Registration Template . . . . . . . . . . . . . . . . 21 4.1.2. Initial Registry Contents . . . . . . . . . . . . . . 22 4.2. OAuth Token Endpoint Authentication Methods Registry . . 24 4.2.1. Registration Template . . . . . . . . . . . . . . . . 25 4.2.2. Initial Registry Contents . . . . . . . . . . . . . . 25 5. Security Considerations . . . . . . . . . . . . . . . . . . . 25 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 29 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.1. Normative References . . . . . . . . . . . . . . . . . . 30 7.2. Informative References . . . . . . . . . . . . . . . . . 31Show full document text