[OpenID] Google custom discovery

[Eric Sachs]

We wonder about the same questions.
For URL validation use cases (which frequently are different then
single-signon), we think it makes sense to provide an OpenID endpoint that
returns those URLs as claimed URLs (whether they are Blogger URLs, Google
Profile URLs, Youtube URLs, etc.

However most of the demand we are seeing for returning Profile URLs is when
they are combined with single-signon, and in those cases the relying parties
do want a way to get them as an AX attribute.  In Google's case it gets
further complicated by the fact that user's have different "profiles" at
Google that they might want returned, and forcing users to pick one for each
RP hurts usability.  And then further complicated by the fact that some RPs
only want to accept profile URLs of a certain type.  And more complicated
still by the fact that most Google users don't have a profile of any type,
so being asked to create one during a sign-on process is extremely
confusing.


On Fri, Jul 10, 2009 at 1:39 PM, Allen Tom <atom at yahoo-inc.com> wrote:

> Would it make sense for Profile URLs to be OpenIDs, or should the Profile
> URL be an attribute that is shared via AX?
>
> What about users who already have both a Profile and an OpenID (with
> different urls) from their OP? Should the Profile URL be delegated to the
> OpenID, or should they be kept separate?
>
> In the interest of interop, it would be great if the community could come
> up with best practices for combining Profiles and OpenIDs.
>
> Allen
>
>
> Eric Sachs wrote:
>
>> Only a subset of GoogleProfile users register a username, but yes, for
>> those users that is the common request we get.
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20090713/1058ced6/attachment.htm>