draft-ietf-oauth-dyn-reg-04.txt   draft-ietf-oauth-dyn-reg-05.txt 
Network Working Group J. Richer, Ed. Network Working Group J. Richer, Ed.
Internet-Draft The MITRE Corporation Internet-Draft The MITRE Corporation
Intended status: Standards Track J. Bradley Intended status: Standards Track J. Bradley
Expires: July 11, 2013 Ping Identity Expires: August 10, 2013 Ping Identity
M. Jones M. Jones
Microsoft Microsoft
M. Machulak M. Machulak
Newcastle University Newcastle University
January 7, 2013 February 6, 2013
OAuth Dynamic Client Registration Protocol OAuth Dynamic Client Registration Protocol
draft-ietf-oauth-dyn-reg-04 draft-ietf-oauth-dyn-reg-05
Abstract Abstract
This specification defines an endpoint and protocol for dynamic This specification defines an endpoint and protocol for dynamic
registration of OAuth Clients at an Authorization Server. registration of OAuth Clients at an Authorization Server.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 11, 2013. This Internet-Draft will expire on August 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 12 skipping to change at page 2, line 12
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Requirements . . . . . . . . . . . . . . . . . . . . . . . 4 2. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.1. The client needs to be uniquely identifiable by 3. Client Registration Endpoint . . . . . . . . . . . . . . . . . 7
the authorization server . . . . . . . . . . . . . . . 4 3.1. Client Registration Request . . . . . . . . . . . . . . . 8
1.3.2. The authorization server must collect metadata 3.2. Client Registration Response . . . . . . . . . . . . . . . 8
about a client for later user interaction . . . . . . 4 3.3. Client Registration Error Response . . . . . . . . . . . . 10
1.3.3. The authorization server should have the option of 4. Client Update Endpoint . . . . . . . . . . . . . . . . . . . . 11
strongly authenticating the client and its metadata . 4 4.1. Client Update Request . . . . . . . . . . . . . . . . . . 12
1.3.4. Dynamic client registration must be possible from 4.2. Client Read Request . . . . . . . . . . . . . . . . . . . 12
both web-server applications and applications with 4.3. Client Update or Read Response . . . . . . . . . . . . . . 13
other capabilities and limitations, such as native 4.4. Client Delete Request . . . . . . . . . . . . . . . . . . 14
applications . . . . . . . . . . . . . . . . . . . . . 4 5. Client Secret Rotation . . . . . . . . . . . . . . . . . . . . 15
1.3.5. Transaction integrity must be ensured . . . . . . . . 5 5.1. Rotate Secret Request . . . . . . . . . . . . . . . . . . 15
2. Client Metadata . . . . . . . . . . . . . . . . . . . . . . . 5 5.2. Rotate Secret Response . . . . . . . . . . . . . . . . . . 15
3. Client Registration Endpoint . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
3.1. Client Registration Request . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
3.2. Client Registration Response . . . . . . . . . . . . . . . 10 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
3.3. Client Update Request . . . . . . . . . . . . . . . . . . 11 9. Document History . . . . . . . . . . . . . . . . . . . . . . . 18
3.4. Client Update Response . . . . . . . . . . . . . . . . . . 13 10. Normative References . . . . . . . . . . . . . . . . . . . . . 20
3.5. Rotate Secret Request . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6. Rotate Secret Response . . . . . . . . . . . . . . . . . . 14
3.7. Client Registration Error Response . . . . . . . . . . . . 15
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
5. Security Considerations . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
7. Document History . . . . . . . . . . . . . . . . . . . . . . . 17
8. Normative References . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
In some use-case scenarios, it is desirable or necessary to allow In some use-case scenarios, it is desirable or necessary to allow
OAuth clients to obtain authorization from an OAuth authorization OAuth clients to obtain authorization from an OAuth authorization
server without requiring the two parties to interact before hand. server without requiring the two parties to interact before hand.
Nevertheless, in order for the authorization server to accurately and Nevertheless, in order for the authorization server to accurately and
securely represent to end-users which client is seeking authorization securely represent to end-users which client is seeking authorization
to access the end-user's resources, a method for automatic and unique to access the end-user's resources, a method for automatic and unique
registration of clients is needed. The OAuth2 authorization registration of clients is needed. The OAuth2 authorization
skipping to change at page 3, line 48 skipping to change at page 3, line 48
This specification uses the terms "Access Token", "Refresh Token", This specification uses the terms "Access Token", "Refresh Token",
"Authorization Code", "Authorization Grant", "Authorization Server", "Authorization Code", "Authorization Grant", "Authorization Server",
"Authorization Endpoint", "Client", "Client Identifier", "Client "Authorization Endpoint", "Client", "Client Identifier", "Client
Secret", "Protected Resource", "Resource Owner", "Resource Server", Secret", "Protected Resource", "Resource Owner", "Resource Server",
and "Token Endpoint" defined by OAuth 2.0 [RFC6749]. and "Token Endpoint" defined by OAuth 2.0 [RFC6749].
This specification defines the following additional terms: This specification defines the following additional terms:
o Client Registration Endpoint: The OAuth 2.0 Endpoint through which o Client Registration Endpoint: The OAuth 2.0 Endpoint through which
a Client can request new registration and manage the metadata a Client can request new registration.
associated with it.
o Client Update Endpoint: The OAuth 2.0 Endpoint through which a
specific Client can manage its registration information, provided
by the Authorization Server to the Client.
o Client Secret Rotation Endpoint: The OAuth 2.0 Endpoint through
which a specific Client can request refreshes of its Client Secret
and Registration Access Token.
o Registration Access Token: An OAuth 2.0 Bearer Token issued by the o Registration Access Token: An OAuth 2.0 Bearer Token issued by the
Authorization Server through the Client Registration Endpoint Authorization Server through the Client Registration Endpoint
which is used by the Client to authenticate itself during update which is used by the Client to authenticate itself during update
and secret rotation operations. and secret rotation operations. This token is associated with a
particular Client.
1.3. Requirements
[[ Following are proposed requirements for dynamic client
registration. This section is intended for discussion and will
likely be removed in the final draft. ]]
1.3.1. The client needs to be uniquely identifiable by the
authorization server
In order for an authorization server to do proper user-delegated
authorization and prevent unauthorized access it must be able to
identify clients uniquely. As is done today in OAuth, the client
identifier (and optional secret) should thus be issued by the
authorization server and not simply accepted as proposed by the
client.
1.3.2. The authorization server must collect metadata about a client
for later user interaction
In order for the authorization server to describe a client to an end-
user in an authorization step it needs information about the client.
This can be the client name at a minimum, but today servers usually
request at least a description, a homepage URL, and an icon when
doing manual registration.
1.3.3. The authorization server should have the option of strongly
authenticating the client and its metadata
In order to prevent spoofing of clients and enable dynamic building
of strong trust relationships, the authorization server should have
the option to verify the provided information. This might be solved
using message signature verification.
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
Each instance of a native application (that is, the specific instance
running on each device) that is installed and run by the same user
may need the option of getting a unique client identifier. In this
case, there are implications around gathering and displaying enough
information to ensure that the end-user is delegating authorization
to the intended application. The registration protocol should be
simple and flexible enough to allow for multiple types of
applications.
1.3.5. Transaction integrity must be ensured
When a client sends information to a server endpoint, it might take
time for this data to propagate through big server installations that
spread across various data centers. Care needs to be taken that
subsequent interactions with the user after the registration process,
such as an authorization request, show the correct data.
2. Client Metadata 2. Client Metadata
Clients generally have an array of metadata associated with their Clients generally have an array of metadata associated with their
unique Client Identifier at the Authorization Server. These can unique Client Identifier at the Authorization Server. These can
range from human-facing display strings, such as a client name, to range from human-facing display strings, such as a client name, to
items that impact the security of the protocol, such as the list of items that impact the security of the protocol, such as the list of
valid redirect URIs. valid redirect URIs.
Extensions and profiles of this specification MAY expand this list, Extensions and profiles of this specification MAY expand this list,
but MUST at least accept all parameters on this list. The but MUST at least accept all parameters on this list. The
Authorization Server MUST ignore any additional parameters sent by Authorization Server MUST ignore any additional parameters sent by
the Client that it does not understand. the Client that it does not understand.
[[ Editor's note: normative language in the table below is meant to
apply to the *client* when sending the request. The paragraph above
is meant to say that the server must at least accept all parameters
and not fail with an error at an unknown parameter, especially if
it's in the list below. Also, extensions need to explicitly call out
if they're not going to do something with one of these basic
parameters instead of just ignoring their existence. This is meant
to be the *minimum set* of parameters for interoperability. ]]
redirect_uris redirect_uris
RECOMMENDED. A space-delimited list of redirect URIs for use in RECOMMENDED. A list of redirect URIs for use in the Authorization
the Authorization Code and Implicit grant types. An Authorization Code and Implicit grant types. An Authorization Server SHOULD
Server SHOULD require registration of valid redirect URIs for all require registration of valid redirect URIs for all clients that
clients to protect against token and credential theft attacks. use these grant types in order to protect against token and
credential theft attacks.
client_name client_name
RECOMMENDED. Human-readable name of the Client to be presented to RECOMMENDED. Human-readable name of the Client to be presented to
the user. If omitted, the Authorization Server MAY display to the the user. If omitted, the Authorization Server MAY display to the
user the raw client_id value instead. user the raw "client_id" value instead.
client_url client_url
RECOMMENDED. URL of the homepage of the Client. If present, the RECOMMENDED. URL of the homepage of the Client. If present, the
server SHOULD display this URL to the end user in a clickable server SHOULD display this URL to the end user in a clickable
fashion. fashion.
logo_url logo_url
OPTIONAL. URL that references a logo for the Client application. OPTIONAL. URL that references a logo for the Client. If present,
If present, the server SHOULD display this image to the end user the server SHOULD display this image to the end user during
during approval. approval.
contacts contacts
OPTIONAL. Space delimited list of email addresses for people OPTIONAL. List of email addresses for people responsible for this
responsible for this client. The Authorization Server MAY may Client. The Authorization Server MAY make these addresses
these addresses available to end users for support queries. An available to end users for support requests for the Client. An
Authorization Server MAY use these email addresses as identifiers Authorization Server MAY use these email addresses as identifiers
for an administrative page for this client. for an administrative page for this client.
tos_url tos_url
OPTIONAL. URL that points to a human-readable Terms of Service OPTIONAL. URL that points to a human-readable Terms of Service
for the Client. The Authorization Server SHOULD display this URL for the Client. The Authorization Server SHOULD display this URL
to the End-User if it is given. to the End-User if it is given.
token_endpoint_auth_type token_endpoint_auth_method
OPTIONAL. The requested authentication type for the Token OPTIONAL. The requested authentication type for the Token
Endpoint. Valid values are: Endpoint. Valid values are:
* "none": this is a public client as defined in OAuth 2.0 and * "none": this is a public client as defined in OAuth 2.0 and
does not have a client secret does not have a client secret
* "client_secret_post": the client uses the HTTP POST parameters * "client_secret_post": the client uses the HTTP POST parameters
defined in OAuth2.0 section 2.3.1 defined in OAuth2.0 section 2.3.1
* "client_secret_basic": the client uses HTTP Basic defined in * "client_secret_basic": the client uses HTTP Basic defined in
OAuth 2.0 section 2.3.1 OAuth 2.0 section 2.3.1
* "client_secret_jwt": the client uses the JWT Assertion profile * "client_secret_jwt": the client uses the JWT Assertion profile
with a symmetric secret issued by the server with a symmetric secret issued by the server
* "private_key_jwt": the client uses the JWT Assertion profile * "private_key_jwt": the client uses the JWT Assertion profile
with its own private key with its own private key
Other Authentication methods may be defined by extension. If Other authentication methods may be defined by extension. If
unspecified or omitted, the default is "client_secret_basic", unspecified or omitted, the default is "client_secret_basic",
denoting HTTP Basic Authentication Scheme as specified in Section denoting HTTP Basic Authentication Scheme as specified in Section
2.3.1 of OAuth 2.0. 2.3.1 of OAuth 2.0.
scope scope
OPTIONAL. Space separated list of scopes that the client will be OPTIONAL. Space separated list of scopes (as described in OAuth
allowed to request tokens for. If omitted, an Authorization 2.0 Section 3.3 [RFC6749]) that the client will be allowed to
Server MAY register a Client with a default set of allowed scopes. request tokens for. If omitted, an Authorization Server MAY
register a Client with a default set of allowed scopes.
grant_type grant_type
OPTIONAL. Space separated list of grant types that a client may OPTIONAL. List of grant types that a client may use. These grant
use. These grant types are defined as follows: types are defined as follows:
* "authorization_code": The Authorization Code Grant described in * "authorization_code": The Authorization Code Grant described in
OAuth2 Section 4.1. OAuth2 Section 4.1.
* "implicit": The Implicit Grant described in OAuth2 Section 4.2. * "implicit": The Implicit Grant described in OAuth2 Section 4.2.
* "password": The Resource Owner Password Credentials Grant * "password": The Resource Owner Password Credentials Grant
described in OAuth2 Section 4.3 described in OAuth2 Section 4.3
* "client_credentials": The Client Credentials Grant described in * "client_credentials": The Client Credentials Grant described in
OAuth2 Section 4.4 OAuth2 Section 4.4
* "refresh_token": The Refresh Token Grant described in OAuth2 * "refresh_token": The Refresh Token Grant described in OAuth2
Section 6. Section 6.
Authorization Servers MAY allow for other values as defined in Authorization Servers MAY allow for other values as defined in
grant type extensions to OAuth2. The extension process is grant type extensions to OAuth2. The extension process is
described in OAuth2 Section 2.5, and the value of this parameter described in OAuth2 Section 2.5, and the value of this parameter
MUST be the same as the value of the grant_type parameter defined MUST be the same as the value of the "grant_type" parameter
in the extension. defined in the extension.
policy_url policy_url
OPTIONAL. A URL location that the Client provides to the End-User OPTIONAL. A URL location that the Client provides to the End-User
to read about the how the profile data will be used. The to read about the how the profile data will be used. The
Authorization Server SHOULD display this URL to the End-User if it Authorization Server SHOULD display this URL to the End-User if it
is given. is given.
jwk_url jwk_url
OPTIONAL. URL for the Client's JSON Web Key [JWK] document that OPTIONAL. URL for the Client's JSON Web Key [JWK] document that
is used for signing requests, such as requests to the Token is used for signing requests, such as requests to the Token
skipping to change at page 7, line 48 skipping to change at page 7, line 17
Certificate chain that is used for signing requests, such as Certificate chain that is used for signing requests, such as
requests to the Token Endpoint using the "private_key_jwt" requests to the Token Endpoint using the "private_key_jwt"
assertion client credential. If the Client registers both assertion client credential. If the Client registers both
"x509_url" and "jwk_url", the keys contained in both formats MUST "x509_url" and "jwk_url", the keys contained in both formats MUST
be the same. be the same.
x509_encryption_url x509_encryption_url
OPTIONAL. URL for the Client's PEM encoded X.509 Certificate or OPTIONAL. URL for the Client's PEM encoded X.509 Certificate or
Certificate chain that the server can use to encrypt responses to Certificate chain that the server can use to encrypt responses to
the Client. If the Client registers both "jwk_encryption_url" and the Client. If the Client registers both "jwk_encryption_url" and
"x509_encryption_url", the keys contained in both formats SHOULD "x509_encryption_url", the keys contained in both formats MUST be
be the same. the same.
3. Client Registration Endpoint 3. Client Registration Endpoint
The Client Registration Endpoint is an OAuth 2.0 Endpoint defined in The Client Registration Endpoint is an OAuth 2.0 Endpoint defined in
this document that is designed to allow a Client to register itself this document that is designed to allow a Client to register itself
with the Authorization Server. The Client Registration Endpoint MUST with the Authorization Server. The Client Registration Endpoint MUST
accept HTTP POST messages with request parameters encoded in the accept HTTP POST messages with request parameters encoded in the
entity body using the "application/x-www-form-urlencoded" format. entity body using the "application/json" format. The Client
The Client Registration Endpoint MUST be protected by a transport- Registration Endpoint MUST be protected by a transport-layer security
layer security mechanism, and the server MUST support TLS 1.2 RFC mechanism, and the server MUST support TLS 1.2 RFC 5246 [RFC5246]
5246 [RFC5246] and/or TLS 1.0 [RFC2246] and MAY support additional and/or TLS 1.0 [RFC2246] and MAY support additional transport-layer
transport-layer mechanisms meeting its security requirements. When mechanisms meeting its security requirements. When using TLS, the
using TLS, the Client MUST perform a TLS/SSL server certificate Client MUST perform a TLS/SSL server certificate check, per RFC 6125
check, per RFC 6125 [RFC6125]. [RFC6125].
The Endpoint defines three operations that a client can take on it,
switched by the "operation" parameter:
o "client_register": request that the Authorization Server generate
a new Client Identifier (and optionally a Client Secret) and
associate it with the set of presented metadata (Section 2)
o "client_update": update the metadata (Section 2) associated with a
Client Identifier
o "rotate_secret": requst a new Registration Access Token and, if
applicable, a Client Secret for a Client
The Client Registration Endpoint MAY accept an initial authorization The Client Registration Endpoint MAY accept an initial authorization
credential in the form of an OAuth 2.0 [RFC6749] access token in credential in the form of an OAuth 2.0 [RFC6749] access token in
order to limit registration to only previously authorized parties. order to limit registration to only previously authorized parties.
The method by which this access token is obtained by the registrant The method by which this access token is obtained by the registrant
is generally out-of-band and is out of scope of this specification. is generally out-of-band and is out of scope of this specification.
In order to support open registration and facilitate wider In order to support open registration and facilitate wider
interoperability, the Client Registration Endpoint SHOULD allow interoperability, the Client Registration Endpoint SHOULD allow
initial "client_register" requests with no authentication. These initial registration requests with no authentication. These requests
requests MAY be rate-limited or otherwise limited to prevent a MAY be rate-limited or otherwise limited to prevent a denial-of-
denial-of-service attack on the Client Registration Endpoint. service attack on the Client Registration Endpoint.
In order to facilitate registered clients updating their information, In order to facilitate registered clients updating their information,
the Client Registration Endpoint issues a Request Access Token for the Client Registration Endpoint issues a Request Access Token for
clients to securely identify themselves in future connections. As clients to securely identify themselves in future connections to the
such, the Endpoint MUST accept requests with OAuth 2.0 Bearer Tokens Client Update Endpoint. As such, the Client Update Endpoint MUST
[RFC6750] for these operations, whether or not the initial accept requests with OAuth 2.0 Bearer Tokens [RFC6750] for these
"client_register" call requires authentication of some form. operations, whether or not the initial registration call requires
authentication of some form.
These two aspects, operation selection and client authentication, are
represented by two parameters common to all operations:
operation
REQUIRED. Valid values are "client_register", "rotate_secret",
and "client_update", as described above.
access_token
OPTIONAL. An OAuth2 Bearer token used to access the Client
Registration Endpoint, as defined in OAuth2 Bearer [RFC6750].
This parameter MUST NOT be sent if the Access Token is sent in the
HTTP Authorization header as described in Section 7.1 of OAuth 2.0
[RFC6749]. Access Tokens sent in the authorization header must be
OAuth 2.0 Bearer Tokens [RFC6750].
Each operation takes a different parameter set, and all operations
are described below.
The Client Registration Endpoint MUST ignore all parameters it does The Client Registration Endpoint MUST ignore all parameters it does
not understand. not understand.
3.1. Client Registration Request 3.1. Client Registration Request
This operation registers a new client to the Authorization Server. This operation registers a new Client to the Authorization Server.
The Authorization Server assigns this client a unique Client The Authorization Server assigns this client a unique Client
Identifier, optionally assigns a Client Secret, and associates the Identifier, optionally assigns a Client Secret, and associates the
metadata given in the request with the issued Client Identifier. The metadata given in the request with the issued Client Identifier. The
request includes the two parameters described above as well as any request includes any parameters described in Client Metadata
parameters described in Client Metadata (Section 2). The (Section 2) that the client wishes to specify for itself during the
Authorization Server MAY provision default values for any items registration. The Authorization Server MAY provision default values
omitted in the Client Metadata. for any items omitted in the Client Metadata.
The Client sends an HTTP POST to the Client Registration Endpoint
with a content type of "application/json" and all parameters as top-
level members of a JSON object.
operation
REQUIRED. MUST have the value "client_register"
access_token
OPTIONAL. OAuth2 Access token used to restrict new client
registration. This parameter MUST NOT be sent if the Access Token
is sent in the HTTP Authorization header as described in Section
7.1 of OAuth 2.0 [RFC6749]. Access Tokens sent in the
authorization header must be OAuth 2.0 Bearer Tokens [RFC6750].
redirect_uris RECOMMENDED
client_name RECOMMENDED
client_url RECOMMENDED
logo_url OPTIONAL
contacts OPTIONAL
tos_url OPTIONAL
token_endpoint_auth_type OPTIONAL
policy_url OPTIONAL
scope OPTIONAL
grant_type OPTIONAL
jwk_url OPTIONAL
jwk_encryption_url OPTIONAL
x509_url OPTIONAL
x509_encryption_url OPTIONAL
For example, a client could send the following registration request For example, a client could send the following registration request
to the Client Registration Endpoint: to the Client Registration Endpoint:
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
POST /register HTTP/1.1 POST /register HTTP/1.1
Accept: application/x-www-form-urlencoded Accept: application/json
Host: server.example.com Host: server.example.com
operation=client_register {
&redirect_uris=https://client.example.org/callback "redirect_uris":["https://client.example.org/callback",
%20https://client.example.org/callback2 "https://client.example.org/callback2"]
&client_name=My%20Example%20Client "client_name":"My Example Client",
&token_endpoint_auth_type=client_secret_basic%20client_secret_post "token_endpoint_auth_method":"client_secret_basic",
&scope=read%20write%20dolphin "scope":"read write dolphin",
&logo_url=https://client.example.org/logo.png "logo_url":"https://client.example.org/logo.png",
&jwk_url=https://client.example.org/my_rsa_public_key.jwk "jwk_url":"https://client.example.org/my_rsa_public_key.jwk"
}
3.2. Client Registration Response 3.2. Client Registration Response
Upon successful registration, the Client Registration Endpoint Upon successful registration, the Client Registration Endpoint
returns the newly-created Client Identifier and, if applicable, a returns the newly-created Client Identifier and, if applicable, a
Client Secret, along with all registered metadata (Section 2) about Client Secret.
this client, including any fields provisioned by the Authorization
Server itself. The Authorization Server MAY reject or replace any of
the client's requested field values and substitute them with suitable
values. If this happens, the Authorization Server MUST include these
fields in the response to the client.
The response also contains a Registration Access Token that is to be Additionally, the Authorization Server SHOULD return all registered
used by the client to perform subsequent operations at this endpoint, metadata (Section 2) about this client, including any fields
such as "client_update" and "rotate_secret". provisioned by the Authorization Server itself. The Authorization
Server MAY reject or replace any of the client's requested metadata
values submitted during the registration request and substitute them
with suitable values. If the Authorization Server performs any such
substitutions to the requested values, it MUST return these values in
the response.
All of the response items are returned as a JSON document [RFC4627] The response contains a "_links" structure which contains fully
with the following fields as top-level members of the root JSON qualified URLs to the Client Update Endpoint and the Client Secret
object. Rotation Endpoint for this specific client. The response also
contains a Registration Access Token that is to be used by the client
to perform subsequent operations at the Client Update Endpoint and
the Client Secret Rotation Endpoint.
The response is an "application/json" document with the following
parameters in addition to any applicable client metadata fields as
top-level members of a JSON object [RFC4627] .
client_id client_id
REQUIRED. The unique Client identifier, MUST NOT be currently REQUIRED. The unique Client identifier, MUST NOT be currently
valid for any other registered Client. valid for any other registered Client.
client_secret client_secret
OPTIONAL. The Client secret. This MUST be unique for each OPTIONAL. The Client secret. If issued, this MUST be unique for
"client_id". This value is used by confidential clients to each "client_id". This value is used by confidential clients to
authenticate to the Token Endpoint as described in OAuth 2.0 authenticate to the Token Endpoint as described in OAuth 2.0
Section 2.3.1. Section 2.3.1.
registration_access_token registration_access_token
REQUIRED. The Access token to be used by the client to perform REQUIRED. The Access token to be used by the client to perform
"client_update" and "rotate_secret" requests. actions on the Client Update Endpoint and the Client Secret
Rotation Endpoint.
issued_at issued_at
OPTIONAL. Specifies the timestamp when the Client Identifier was OPTIONAL. Specifies the timestamp when the Client Identifier was
issued. The timestamp value MUST be a positive integer. The issued. The timestamp value MUST be a positive integer. The
value is expressed in the number of seconds since January 1, 1970 value is expressed in the number of seconds since January 1, 1970
00:00:00 GMT. 00:00:00 GMT.
expires_at expires_at
OPTIONAL. The number of seconds from 1970-01-01T0:0:0Z as REQUIRED if "client_secret" is issued. The number of seconds from
measured in UTC that the "client_secret" will expire or "0" if 1970-01-01T0:0:0Z as measured in UTC that the "client_secret" will
they do not expire. See RFC 3339 [RFC3339] for details regarding expire or "0" if it does not expire. See RFC 3339 [RFC3339] for
date/times in general and UTC in particular. details regarding date/times in general and UTC in particular.
_links
REQUIRED. A JSON object that contains references to the Client
Update Endpoint and Client Secret Rotation Endpoint, via the
following members:
self REQUIRED. A JSON object that contains the member href which
contains the fully qualified URL of the Client Update Endpoint
for this client. This MAY be constructed using a URL Template
of the Client Registration Endpoint with the issued client_id.
rotate_secret REQUIRED. A JSON object that contains the member
href which contains the fully qualified URL of the Client
Secret Rotation Endpoint for this client. This MAY be
constructed using a URL Template of the Client Registration
Endpoint with the issued client_id.
Following is a non-normative example response: Following is a non-normative example response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Type: application/json Content-Type: application/json
Cache-Control: no-store Cache-Control: no-store
{ {
"client_id":"s6BhdRkqt3", _links: {
"client_secret": "cf136dc3c1fc93f31185e5885805d", "self": {
"scope": "read write dolphin", "href":
"grant_type": "authorization_code refresh_token", "https://server.example.com/register/s6BhdRkqt3"
"token_endpoint_auth_type": "client_secret_basic client_secret_post", },
"logo_url": "https://client.example.org/logo.png", "rotate_secret": {
"jwk_url": "https://client.example.org/my_rsa_public_key.jwk", "href":
"registration_access_token": "reg-23410913-abewfq.123483", "https://server.example.com/register/rotate_secret/s6BhdRkqt3"
"expires_at":2893276800 }
} "redirect_uris":["https://client.example.org/callback",
"https://client.example.org/callback2"]
"client_id":"s6BhdRkqt3",
"client_secret": "cf136dc3c1fc93f31185e5885805d",
"scope": "read write dolphin",
"grant_type": ["authorization_code", "refresh_token"]
"token_endpoint_auth_method": "client_secret_basic",
"logo_url": "https://client.example.org/logo.png",
"jwk_url": "https://client.example.org/my_rsa_public_key.jwk",
"registration_access_token": "reg-23410913-abewfq.123483",
"expires_at":2893276800
}
3.3. Client Update Request 3.3. Client Registration Error Response
When an OAuth error condition occurs, the Client Registration
Endpoint returns an Error Response as defined in Section 5.2 of the
OAuth 2.0 specification.
When a registration error condition occurs, the Client Registration
Endpoint returns a HTTP 400 status code including a JSON object
[RFC4627] describing the error in the response body.
The JSON object contains two members:
error
The error code, a single ASCII string.
error_description
The additional text description of the error for debugging.
This specification defines the following error codes:
invalid_redirect_uri
The value of one or more "redirect_uris" is invalid.
invalid_client_metadata
The value of one of the client metadata (Section 2) fields is
invalid and the server has rejected this request. Note that an
Authorization server MAY choose to substitute a valid value for
any requested parameter of a client's metadata.
Following is a non-normative example of an error response (with line
wraps for display purposes only):
HTTP/1.1 400 Bad Request
Content-Type: application/json
Cache-Control: no-store
{
"error":"invalid_redirect_uri",
"error_description":"The redirect URI of http://sketchy.example.com
is not allowed for this server."
}
4. Client Update Endpoint
The Client Update Endpoint is an OAuth 2.0 protected endpoint that is
provisioned by the server for a specific client to be able to view
and update its registered information. It is RECOMMENDED that this
endpoint URL be formed through the use of a URL template which
combines the Client Registration Endpoint and the issued client_id
for this client, either as a path parameter
(https://server.example.com/register/client_id) or as a query
parameter (https://server.example.com/register/?update=client_id).
The Authorization Server MUST provide the client with the fully
qualified URL in the _links structure described in section 3 and MUST
NOT require the client to construct this URL on its own.
The Authorization Server MUST be able to determine the appropriate
client_id from the context of the request without requiring the
Client to explicitly send its own "client_id" in the request.
Operations on this endpoint are switched through the use of specific
HTTP verbs.
4.1. Client Update Request
This operation updates a previously-registered client with new This operation updates a previously-registered client with new
metadata at the Authorization Server. This request MUST be protected metadata at the Authorization Server. This request is authenticated
by the Registration Authorization Token associated with the Client. by the Registration Access Token issued to the client.
This request MAY include any fields described in Client Metadata The Client makes an HTTP PUT request to the Client Update Endpoint
(Section 2). If included in the request, valid values of Client with a content type of "application/json". This request MAY include
Metadata fields in this request MUST replace, not augment, the values any fields described in Client Metadata (Section 2). If included in
previously associated with this Client. Empty values in Client the request, valid values of Client Metadata fields in this request
MUST replace, not augment, the values previously associated with this
Client. Any fields with the value of a JSON "null" in Client
Metadata MUST be taken as a request to clear any existing value of Metadata MUST be taken as a request to clear any existing value of
that field. Omitted values in the Client Metadata MUST remain that field. Omitted values in the Client Metadata MUST remain
unchanged by the Authorization Server. The Authorization Server MAY unchanged by the Authorization Server. The Authorization Server MAY
replace any invalid values with suitable values. replace any invalid values with suitable values, and it MUST return
any such fields to the Client in the response.
operation
REQUIRED, MUST have the value "client_update"
access_token
REQUIRED, unless presented in the Authorization Header as in
OAuth2 Bearer [RFC6750]. The Registration Access Token that was
issued during the "client_register" step, or previous
"client_update" or "rotate_secret" calls.
redirect_uris RECOMMENDED
client_name RECOMMENDED
client_url RECOMMENDED
logo_url OPTIONAL
contacts OPTIONAL
tos_url OPTIONAL
token_endpoint_auth_type OPTIONAL
policy_url OPTIONAL
jwk_url OPTIONAL
jwk_encryption_url OPTIONAL
x509_url OPTIONAL
x509_encryption_url OPTIONAL
For example, a client could send the following request to the Client For example, a client could send the following request to the Client
Registration Endpoint to update the client registration in the above Registration Endpoint to update the client registration in the above
example: example:
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
POST /register HTTP/1.1 PUT /register/s6BhdRkqt3 HTTP/1.1
Accept: application/x-www-form-urlencoded Accept: application/json
Host: server.example.com Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483 Authorization: Bearer reg-23410913-abewfq.123483
operation=client_update {
&redirect_uri=https://client.example.org/callback "redirect_uri":["https://client.example.org/callback",
%20https://client.example.org/alt "https://client.example.org/alt"],
&client_name=My%20New%20Example%20 "client_name":"My New Example",
&logo_url=https://client.example.org/newlogo.png "logo_url":"https://client.example.org/newlogo.png"
}
3.4. Client Update Response 4.2. Client Read Request
Upon successful update, the Client Registration Endpoint returns the In order to read the current configuration of the Client on the
Client ID, along with all current registered metadata (Section 2) Authorization Server, the Client makes an HTTP GET request to the
about this client, including any fields provisioned by the Client Update Endpoint with the Registration Access Token.
Authorization Server itself. The Authorization Server MAY reject or
replace any of the client's requested field values and substitute Following is a non-normative example request (with line wraps for
them suitable values. If this happens, the Authorization Server MUST display purposes only):
include these fields in the response to the client. GET /register/s6BhdRkqt3 HTTP/1.1
Accept: application/json
Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483
4.3. Client Update or Read Response
Upon successful update or read operation, the Client Update Endpoint
returns the Client ID. Additionally, the Authorization Server SHOULD
return all registered metadata (Section 2) about this client,
including any fields provisioned by the Authorization Server itself.
The Authorization Server MAY reject or replace any of the client's
requested metadata values submitted during an update request and
substitute them with suitable values. If the Authorization Server
performs any such substitutions to the requested values, it MUST
return these values in the response.
The Authorization Server MUST NOT include the Client Secret or The Authorization Server MUST NOT include the Client Secret or
Request Access Token in this response. Request Access Token in this response.
These fields are returned in a JSON Document [RFC4627] as top-level The response is a JSON Document [RFC4627] with the following fields
members of the root JSON object. as well as any applicable client metadata as top-level members of a
JSON object.
client_id client_id
REQUIRED. The unique Client identifier, MUST equal the value of REQUIRED. The unique Client identifier, MUST equal the value of
the client_id returned in the original client_register request. the client_id returned in the original client_register request.
Following is a non-normative example response: _links
HTTP/1.1 200 OK REQUIRED. A JSON object that contains references to the Client
Content-Type: application/json Update Endpoint and Client Secret Rotation Endpoint, via the
Cache-Control: no-store following members:
{ self REQUIRED. A JSON object that contains the member href which
"client_id": "s6BhdRkqt3", contains the fully qualified URL of the Client Update Endpoint
"client_name": "My New Example", for this client. This MAY be constructed using a URL Template
"redirect_uri": of the Client Registration Endpoint with the issued client_id.
"https://client.example.org/callback https://client.example.org/alt"
"scope": "read write dolphin",
"grant_type": "authorization_code refresh_token",
"token_endpoint_auth_type": "client_secret_basic client_secret_post",
"logo_url": "https://client.example.org/newlogo.png",
"jwk_url": "https://client.example.org/my_rsa_public_key.jwk",
}
3.5. Rotate Secret Request rotate_secret REQUIRED. A JSON object that contains the member
href which contains the fully qualified URL of the Client
Secret Rotation Endpoint for this client. This MAY be
constructed using a URL Template of the Client Registration
Endpoint with the issued client_id.
This operation allows the client to rotate its current Registration Following is a non-normative example response:
Access Token as well as its Client Secret, if it has one. HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
operation {
REQUIRED. MUST have the value rotate_secret _links: {
"self": {
"href": "https://server.example.com/register/s6BhdRkqt3"
},
"rotate_secret": {
"href": "https://server.example.com/register/s6BhdRkqt3/secret"
}
"client_id": "s6BhdRkqt3",
"client_name": "My New Example",
"redirect_uri": ["https://client.example.org/callback",
"https://client.example.org/alt"]
"scope": "read write dolphin",
"grant_type": ["authorization_code", "refresh_token"],
"token_endpoint_auth_method": "client_secret_basic",
"logo_url": "https://client.example.org/newlogo.png",
"jwk_url": "https://client.example.org/my_rsa_public_key.jwk",
}
access_token 4.4. Client Delete Request
REQUIRED, unless presented in the Authorization Header as in
OAuth2 Bearer [RFC6750]. The Registration Access Token that was In order to deprovision itself on the Authorization Server, the
issued during the "client_register" step, or previous Client makes an HTTP DELETE request to the Client Update Endpoint
"client_update" or "rotate_secret" calls. with the Registration Access Token. This request is authenticated by
the Registration Access Token issued to the client.
Following is a non-normative example request (with line wraps for Following is a non-normative example request (with line wraps for
display purposes only): display purposes only):
POST /register HTTP/1.1 DELETE /register/s6BhdRkqt3 HTTP/1.1
Accept: application/x-www-form-urlencoded Accept: application/json
Host: server.example.com Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483 Authorization: Bearer reg-23410913-abewfq.123483
operation=rotate_secret If a client has been successfully deprovisioned, the Authorization
Server responds with an HTTP 204 No Content message.
3.6. Rotate Secret Response Following is a non-normative example response:
HTTP/1.1 204 No Content
Cache-Control: no-store
5. Client Secret Rotation
The Client Secret Rotation Endpoint is an OAuth 2.0 protected
endpoint that is provisioned by the server for a specific client to
be able to request rotation of its Registration Access Token and, if
it has one, Client Secret. It is RECOMMENDED that this endpoint URL
be formed through the use of a URL template which combines the Client
Registration Endpoint and the issued client_id for this client,
either as a path parameter
(https://server.example.com/register/rotate_secret/client_id) or as a
query parameter
(https://server.example.com/register/?rotate_secret=client_id). The
Authorization Server MUST provide the client with the fully qualified
URL in the _links structure described in section 3, and MUST NOT
require the Client to construct this URL on its own.
The Authorization Server MUST be able to determine the appropriate
client_id from the context of the request without requiring the
Client to explicitly send its own "client_id" in the request.
5.1. Rotate Secret Request
This operation allows the client to rotate its current Registration
Access Token as well as its Client Secret, if it has one. The client
sends an HTTP POST with its current Registration Access Token. This
request is authenticated by the Registration Access Token issued to
the client.
Following is a non-normative example request (with line wraps for
display purposes only):
POST /register/rotate_secret/s6BhdRkqt3 HTTP/1.1
Accept: application/json
Host: server.example.com
Authorization: Bearer reg-23410913-abewfq.123483
5.2. Rotate Secret Response
Upon successful rotation of the Registration Access Token, and Upon successful rotation of the Registration Access Token, and
optionally the Client Secret, the Client Registration Endpoint optionally the Client Secret, the Client Registration Endpoint
returns a JSON document [RFC4627] with the following fields as top- returns a JSON document [RFC4627] with the following fields as top-
level members of the root JSON object. This response MUST NOT level members of the root JSON object. This response MUST NOT
include any other client metadata. include any other client metadata.
client_id client_id
REQUIRED. The unique Client identifier, MUST match the client_id REQUIRED. The unique Client identifier, MUST match the client_id
issued in the original client_register request. issued in the original registration request.
client_secret client_secret
REQUIRED if the server initially issued this Client a Client REQUIRED if the server initially issued this Client a Client
Secret, otherwise the server MUST NOT return a value. The value Secret, otherwise the server MUST NOT return a value. The value
MUST be unique for each "client_id". MUST be unique for each "client_id".
registration_access_token registration_access_token
REQUIRED The Access token to be used by the client to perform REQUIRED. The Access token to be used by the client to perform
subsequent "client_update" and "rotate_secret" requests. subsequent "client_update" and "rotate_secret" requests.
issued_at issued_at
OPTIONAL. Specifies the timestamp when the identifier was issued. OPTIONAL. Specifies the timestamp when the identifier was issued.
The timestamp value MUST be a positive integer. The value is The timestamp value MUST be a positive integer. The value is
expressed in the number of seconds since January 1, 1970 00:00:00 expressed in the number of seconds since January 1, 1970 00:00:00
GMT. GMT.
expires_at expires_at
OPTIONAL. The number of seconds from 1970-01-01T0:0:0Z as REQUIRED if the server issues a Client Secret. The number of
measured in UTC that the "client_secret" will expire or "0" if seconds from 1970-01-01T0:0:0Z as measured in UTC that the
they do not expire. See RFC 3339 [RFC3339] for details regarding "client_secret" will expire or "0" if they do not expire. See RFC
date/times in general and UTC in particular. 3339 [RFC3339] for details regarding date/times in general and UTC
in particular.
Following is a non-normative example response: Following is a non-normative example response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
Content-Type: application/json Content-Type: application/json
Cache-Control: no-store Cache-Control: no-store
{ {
"client_id":"s6BhdRkqt3", "client_id":"s6BhdRkqt3",
"client_secret": "7fce6c93f31185e5885805d", "client_secret": "7fce6c93f31185e5885805d",
"registration_access_token": "reg-02348913-oieqer.983421", "registration_access_token": "reg-02348913-oieqer.983421",
"expires_at":2893276800 "expires_at":2893276800
} }
The Authorization Server SHOULD discard and invalidate the Request The Authorization Server SHOULD discard and invalidate the Request
Access Token and the Client Secret associated with this Client after Access Token and the Client Secret associated with this Client after
successful completion of this request. successful completion of this request.
3.7. Client Registration Error Response 6. IANA Considerations
When an OAuth error condition occurs, the Client Registration
Endpoint returns an Error Response as defined in Section 5.2 of the
OAuth 2.0 specification.
When a registration error condition occurs, the Client Registration
Endpoint returns a HTTP 400 status code including a JSON object
[RFC4627] describing the error in the response body.
The JSON object contains two members:
error
The error code, a single ASCII string.
error_description
The additional text description of the error for debugging.
This specification defines the following error codes:
invalid_operation
The value of "operation" is invalid or not supported.
invalid_redirect_uri
The value of one or more "redirect_uris" is invalid.
invalid_client_metadata
The value of one of the client metadata (Section 2) fields is
invalid and the server has rejected this request. Note that an
Authorization server MAY choose to substitute a valid value for
any requested parameter of a client's metadata.
Following is a non-normative example of an error response (with line
wraps for display purposes only):
HTTP/1.1 400 Bad Request
Content-Type: application/json
Cache-Control: no-store
{
"error":"invalid_operation",
"error_description":"The value of the operation parameter must
be one of client_register, rotate_secret or client_update."
}
4. IANA Considerations
This document makes no requests of IANA. This document makes no requests of IANA.
5. Security Considerations 7. Security Considerations
[[ Editor's note: Following are some security considerations taken [[ Editor's note: Following are some security considerations taken
from the UMA and OpenID Connect source drafts. These need to be from the UMA and OpenID Connect source drafts. These need to be
massaged into a properly generic set of considerations. ]] massaged into a properly generic set of considerations. ]]
Since requests to the Client Registration Endpoint result in the Since requests to the Client Registration Endpoint result in the
transmission of clear-text credentials (in the HTTP request and transmission of clear-text credentials (in the HTTP request and
response), the server MUST require the use of a transport-layer response), the server MUST require the use of a transport-layer
security mechanism when sending requests to the Registration security mechanism when sending requests to the Registration
Endpoint. The server MUST support TLS 1.2 RFC 5246 [RFC5246] and/or Endpoint. The server MUST support TLS 1.2 RFC 5246 [RFC5246] and/or
skipping to change at page 17, line 26 skipping to change at page 18, line 4
While the Client Secret can expire, the Registration Access Token While the Client Secret can expire, the Registration Access Token
should not expire while a client is still actively registered. If should not expire while a client is still actively registered. If
this token were to expire, a Client could be left in a situation this token were to expire, a Client could be left in a situation
where it has no means of updating itself and must register itself where it has no means of updating itself and must register itself
anew. As the Registration Access Tokens are long-term credentials, anew. As the Registration Access Tokens are long-term credentials,
they MUST be protected by the Client as a secret. [[ Editor's note: they MUST be protected by the Client as a secret. [[ Editor's note:
with the right error codes returned from client_update, the AS could with the right error codes returned from client_update, the AS could
force the Client to call rotate_secret before going forward, force the Client to call rotate_secret before going forward,
lessening the window for abuse of a leaked registration token. ]] lessening the window for abuse of a leaked registration token. ]]
Since the Registration Access Token is a Bearer token and acts as the
sole authentication for use at the Client Update Endpoint, it MUST be
protected by the Client as described in OAuth 2.0 Bearer [RFC6750].
6. Acknowledgments 8. Acknowledgments
The authors thank the OAuth Working Group, the User-Managed Access The authors thank the OAuth Working Group, the User-Managed Access
Working Group, and the OpenID Connect Working Group participants for Working Group, and the OpenID Connect Working Group participants for
their input to this document. In particular, the following their input to this document. In particular, the following
individuals have been instrumental in their review and contribution individuals have been instrumental in their review and contribution
to various versions of this document: Torsten Lodderstedt, Eve Maler, to various versions of this document: Torsten Lodderstedt, Eve Maler,
Thomas Hardjono, Christian Scholz, Nat Sakimura, George Fletcher, Thomas Hardjono, Christian Scholz, Nat Sakimura, George Fletcher,
Amanda Anganes, and Domenico Catalano. Amanda Anganes, and Domenico Catalano.
7. Document History 9. Document History
[[ to be removed by RFC editor before publication as an RFC ]] [[ to be removed by RFC editor before publication as an RFC ]]
- 05
o changed redirect_uri and contact to lists instead of space
delimited strings
o removed operation parameter
o added _links structure
o made client update management more RESTful
o split endpoint into three parts
o changed input to JSON from form-encoded
o added READ and DELETE operations
o removed Requirements section
o changed token_endpoint_auth_type back to
token_endpoint_auth_method to match OIDC who changed to match us
- 04 - 04
o removed default_acr, too undefined in the general OAuth2 case o removed default_acr, too undefined in the general OAuth2 case
o removed default_max_auth_age, since there's no mechanism for o removed default_max_auth_age, since there's no mechanism for
supplying a non-default max_auth_age in OAuth2 supplying a non-default max_auth_age in OAuth2
o clarified signing and encryption URLs o clarified signing and encryption URLs
o changed token_endpoint_auth_method to token_endpoint_auth_type to o changed token_endpoint_auth_method to token_endpoint_auth_type to
match OIDC match OIDC
- 03 - 03
o added scope and grant_type claims o added scope and grant_type claims
o fixed various typos and changed wording for better clarity o fixed various typos and changed wording for better clarity
o endpoint now returns the full set of client information o endpoint now returns the full set of client information
skipping to change at page 18, line 46 skipping to change at page 20, line 5
o Merged UMA and OpenID Connect registrations into a single document o Merged UMA and OpenID Connect registrations into a single document
o Changed to form-paramter inputs to endpoint o Changed to form-paramter inputs to endpoint
o Removed pull-based registration o Removed pull-based registration
- 00 - 00
o Imported original UMA draft specification o Imported original UMA draft specification
8. Normative References 10. Normative References
[JWK] Jones, M., "JSON Web Key (JWK)", May 2012. [JWK] Jones, M., "JSON Web Key (JWK)", May 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
RFC 2246, January 1999. RFC 2246, January 1999.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
 End of changes. 64 change blocks. 
352 lines changed or deleted 400 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/