[Openid-specs-ab] Fields that the server has provisioned on the client's behalf

Mike Jones Michael.Jones at microsoft.com
Wed Feb 6 06:37:40 UTC 2013


Hi Justin,

In his review comments, Brian wrote:

http://openid.net/specs/openid-connect-registration-1_0-14.html#ClientRegisterResponse
2.2.1.  Client Register Operation Response

This section and 2.2.3 have "Additionally, the server MUST include all registered metadata about a client as described in Section 2.1<http://openid.net/specs/openid-connect-registration-1_0-14.html#ClientRegistration>, including any fields that the server has provisioned on the client's behalf." What is the expected behavior for default values from 2.1 (that very well might not be stored anywhere).

Justin, can you answer Brian's question about the intent of the text about "fields that the server has provisioned on the client's behalf"?  He seems to be raising a point of ambiguity in the registration spec as currently worded.

One aspect of this is whether in an update operation:
(1) the client should be expected to be able to provide new values for these fields that it didn't previously request in its initial reservation request,
(2) the client should be prohibited from providing new values for these fields that it didn't previously request in its initial reservation request,
(3) it is unspecified whether the client can providing new values for these fields that it didn't previously request in its initial reservation request,
(4) whether the client must provide the same values for these fields that it didn't previously request in its initial reservation request.

I believe that if we're going to allow the registration responses to contain the values of fields that were not in the initial registration request and that are potentially not specified in the OpenID Connect specifications, that these questions need to be answered.

                                                            Thanks,
                                                            -- Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130206/56bd36a4/attachment.html>


More information about the Openid-specs-ab mailing list