draft-ietf-oauth-dyn-reg-management-11.txt   draft-ietf-oauth-dyn-reg-management-12.txt 
OAuth Working Group J. Richer, Ed. OAuth Working Group J. Richer, Ed.
Internet-Draft Internet-Draft
Intended status: Experimental M. Jones Intended status: Experimental M. Jones
Expires: September 24, 2015 Microsoft Expires: September 25, 2015 Microsoft
J. Bradley J. Bradley
Ping Identity Ping Identity
M. Machulak M. Machulak
Newcastle University Newcastle University
March 23, 2015 March 24, 2015
OAuth 2.0 Dynamic Client Registration Management Protocol OAuth 2.0 Dynamic Client Registration Management Protocol
draft-ietf-oauth-dyn-reg-management-11 draft-ietf-oauth-dyn-reg-management-12
Abstract Abstract
This specification defines methods for management of dynamic OAuth This specification defines methods for management of dynamic OAuth
2.0 client registrations for use cases in which the properties of a 2.0 client registrations for use cases in which the properties of a
registered client may need to be changed during the lifetime of the registered client may need to be changed during the lifetime of the
client. Not all authorization servers supporting dynamic client client. Not all authorization servers supporting dynamic client
registration will support these management methods. registration will support these management methods.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 September 24, 2015. This Internet-Draft will expire on September 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 11, line 34 skipping to change at page 11, line 34
"https://client.example.org/callback", "https://client.example.org/callback",
"https://client.example.org/callback2"], "https://client.example.org/callback2"],
"grant_types": ["authorization_code", "refresh_token"], "grant_types": ["authorization_code", "refresh_token"],
"token_endpoint_auth_method": "client_secret_basic", "token_endpoint_auth_method": "client_secret_basic",
"logo_uri": "https://client.example.org/logo.png", "logo_uri": "https://client.example.org/logo.png",
"jwks_uri": "https://client.example.org/my_public_keys.jwks" "jwks_uri": "https://client.example.org/my_public_keys.jwks"
} }
4. IANA Considerations 4. IANA Considerations
This specification requests that IANA extend the OAuth Dynamic Client This specification registers the following client metadata names and
Metadata registry with the following entries: descriptions in the OAuth Dynamic Client Registration Metadata
registry established by [OAuth.Registration]:
o Client Metadata Name: "registration_access_token" o Client Metadata Name: "registration_access_token"
o Client Metadata Description: OAuth 2.0 bearer token used to access o Client Metadata Description: OAuth 2.0 bearer token used to access
the client configuration endpoint the client configuration endpoint
o Change controller: IESG o Change controller: IESG
o Specification document(s): [[ this document ]] o Specification document(s): [[ this document ]]
skipping to change at page 16, line 23 skipping to change at page 16, line 23
against the client to which the registration access token was issued. against the client to which the registration access token was issued.
If desired, the server MAY simply return the client registration If desired, the server MAY simply return the client registration
endpoint URL as the client configuration endpoint URL and change endpoint URL as the client configuration endpoint URL and change
behavior based on the authentication context provided by the behavior based on the authentication context provided by the
registration access token. registration access token.
Appendix D. Document History Appendix D. Document History
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
-12
o Used consistent registry name.
-11 -11
o Fixed a series of nits from Peter Yee's Gen-ART review. o Fixed a series of nits from Peter Yee's Gen-ART review.
-10 -10
o Updated author information. o Updated author information.
o Updated TLS information, imported from Dynamic Registration core. o Updated TLS information, imported from Dynamic Registration core.
 End of changes. 6 change blocks. 
6 lines changed or deleted 11 lines changed or added

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