views:

159

answers:

3

Would this be a smart thing to do? I don't want to alienate my users, but having multiple ways to sign in to the site kind of defeats the purpose of having an OpenID implementation. This isn't a brand new site and has about 3k users which are somewhat diehards (we have a great community), but not all of them are and I don't want to lose anyone due to a sign in process.

Is there a simple way to convert the existing accounts into OpenId? or am I going to have to create some kind of "associate with old account".

+5  A: 

To create OpenId's for each user you would need to offer your own identity provider service to have control over these users. And that might require more work than having two authentication ways. I suggest you offer both ways, it's how most sites handle this issue.

driAn
I don't think you'd want to build the ability to creat OpenID's, but have a list of links the user can use so they can creat their own.
Jeremy
Exactly, however rball was refering to "converting existing accounts into OpenID", so he wants to do that automatically without having the user to go through any external site's web wizard. That can only be achieved with an own auth provider you control yourself.
driAn
+2  A: 

The advantage of OpenID is that it allows people to use their existing identity at your site. I don't think having two ways to sign in defeats this purpose, since users without an existing identity will find openID inconvenient.

Brian
A: 

Look at the way UserVoice (used by SO) handles both legacy and OpenID login. They coexist in a straight forward way.

ltd