vimeo cul-de-sac

[Luke Shepard]

Since the beginning, Connect has been intended to work within an existing user system in which multiple identifiers associated with a local id, as you mentioned. In fact, I implemented the original sample application, The Run Around, to have two account types - a native account type that required a password, and a Facebook account type that didn't require one (but you could optionally add one).

What the example "in the wild" have shown is that properly coding a website to have multiple identifiers for a single account is difficult.

Ben, to your question - we have a few lists of best practice sites, although I haven't taken a study specifically of the behavior of sites with respect to how they handle existing user accounts that get merged. I think my favorite implementation of the "single sign on" concept is Citysearch.


On 4/2/09 11:23 PM, "Chris Messina" <chris.messina at gmail.com> wrote:

The problem with FB Connect, as I understand it, is that it presumes that the underlying site has no social graph of its own. This clearly conflicts with sites like Vimeo and Digg that make assumptions about user accounts - i.e. that they have passwords associated with them.

The standard pattern should become associating multiple identifiers with a local GUID, but unfortunately many sites key identity off of a unique email address which clearly has ramifications that must be accounted for as remote identities need to be linked up to existing accounts.

Ben, if you could document this case on the wiki that'd be very useful.

Thanks,

Chris

On Mon, Mar 30, 2009 at 11:45 AM, Ben Clemens <bclemens at currentmedia.com> wrote:
Are there fb connect rps you-all consider the best implementations (handling
these and other cases with aplomb)? Apologies if this was covered at the
conference or before...

On 3/30/09 11:02 AM, "Luke Shepard" <lshepard at facebook.com> wrote:

> Thanks for the feedback, ben. You raise a good point - a lot of RPs have
> struggled with what to do when they don't collect a password. For some Connect
> partners, they have nailed all the use cases, but occasionally we find an edge
> case that's still assuming pw or email.
>
> Others just require a new password anyway- that let's them punt on the
> difficult issues while still getting some of the benefits of a facebook login
> (like feed and profile data)
>
> These are definitely some of the issues we should be educating rps about.
>
> I'll pass this along to vimeo.
>
> ----- Original Message -----
> From: user-experience-bounces at openid.net <user-experience-bounces at openid.net>
> To: user-experience at openid.net <user-experience at openid.net>
> Sent: Mon Mar 30 10:44:53 2009
> Subject: vimeo cul-de-sac
>
> I got into a cul-de-sac today with vimeo facebook connect, and thought it
> would be good to highlight the case so it can be avoided in openid
> interaction.
>
> I have a vimeo account, but wasn't signed-in to it. I wanted to try the
> facebook sign-in, so I clicked the fb button, then got an overlay with prefs
> to allow updates to facebook and the message that a vimeo account had been
> created linked to my facebook account. So far so good.
>
> There's no way on vimeo to link a different vimeo account to the new
> facebook one, but I imagine they will take care of that at some point. What
> got me was that when I wanted to remove the new facebook account I had
> created (since it's useless to me), vimeo asked me to verify my password. I
> hadn't created one, of course, so I was unable to remove the account. Since
> I had already linked my facebook account with an account on vimeo, I
> couldn't fix it afterwards either from my real vimeo account.
>
> best,
> Ben
>
> _______________________________________________
> user-experience mailing list
> user-experience at openid.net
> http://openid.net/mailman/listinfo/user-experience
> _______________________________________________
> user-experience mailing list
> user-experience at openid.net
> http://openid.net/mailman/listinfo/user-experience

_______________________________________________
user-experience mailing list
user-experience at openid.net
http://openid.net/mailman/listinfo/user-experience


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-user-experience/attachments/20090403/814617e9/attachment-0002.htm>