Neither registration_access_token nor registration_client_uri are mentioned in 
core-16. They're both required in the management draft, and it makes sense 
there. If you're not implementing the management draft (or you've got your own 
thing for that), then you don't return either of them.

 -- Justin

________________________________
From: OAuth [oauth-boun...@ietf.org] on behalf of Anthony Nadalin 
[tony...@microsoft.com]
Sent: Thursday, March 06, 2014 11:00 AM
To: Anthony Nadalin; Mike Jones; oauth@ietf.org list
Subject: Re: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic 
Client Registration Specs

Same is true for the registration_client_uri as I may not need/want this, 
should be optional

From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Anthony Nadalin
Sent: Thursday, March 6, 2014 7:02 AM
To: Mike Jones; oauth@ietf.org list
Subject: Re: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic 
Client Registration Specs

So the current core makes the registration_access_token  required and there are 
open registration endpoints, so this should be optional, there are also cases 
where the client_id is signed and that becomes the right to the registration 
endpoint

From: OAuth [mailto:oauth-boun...@ietf.org] On Behalf Of Mike Jones
Sent: Friday, February 7, 2014 10:58 AM
To: oauth@ietf.org<mailto:oauth@ietf.org> list
Subject: [OAUTH-WG] Working Group Versions of Refactored OAuth Dynamic Client 
Registration Specs

There are now OAuth working group<http://datatracker.ietf.org/wg/oauth/> 
versions of the refactored OAuth Dynamic Client Registration specifications:

·         OAuth 2.0 Dynamic Client Registration Core Protocol

·         OAuth 2.0 Dynamic Client Registration Metadata

·         OAuth 2.0 Dynamic Client Registration Management Protocol

These versions address review comments by Phil Hunt and Tony Nadalin.  Phil is 
now also an author.  The data structures and messages used are the same as the 
previous versions<http://self-issued.info/?p=1171>.

The drafts are available at:

·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-16

·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-metadata-00

·         http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-management-00

HTML formatted versions are also available at:

·         https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-16.html

·         
https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-metadata-00.html

·         
https://self-issued.info/docs/draft-ietf-oauth-dyn-reg-management-00.html

                                                            -- Mike

P.S.  I also posted this notice at http://self-issued.info/?p=1180 and as 
@selfissued.

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

Reply via email to