OK thanks. On the verifiable would just like to make sure that aggregation can be before or after verifiable
From: Dick Hardt [mailto:[email protected]] Sent: Wednesday, May 19, 2010 2:25 PM To: Anthony Nadalin Cc: OpenID Specs Mailing List Subject: Re: OpenID v.Next Core Protocol Charter On 2010-05-19, at 2:01 PM, Anthony Nadalin wrote: Some questions > enable aggregation of attributes from multiple verifiable sources Not sure that this should be limited to verifiable sources as verification can be done later I think verification done later means verifiable. :) Happy to adjust if you have alternative wording. > enable support for controlled release of attributes, >From the IdP or User ? either > define an extension mechanism For what? for things we think might be useful or others think would be useful but are determined not to be suitable in core > complement OAuth 2.0 Does this mean work well, integrate, allow OpenID attributes to be used in OAuth flow? An example would be moving an access token within the OpenID response that could be used per OAuth 2.0 -- Dick
_______________________________________________ specs mailing list [email protected] http://lists.openid.net/mailman/listinfo/openid-specs
