Page 1 of 1

OpenID Implamention Suggestion (Need Better wording?)

Posted: Mon Jun 11, 2007 11:53 am
by DaveTheAve
Basically, I was up last night thinking about how i should, or even if I should, implement OpenID for my Clients site. Ether-way, I was thinking about how OpenID is suppose to "replace" usernames and passwords, I don't like that idea at all. What if the user, for what-ever reason, wants to login with a normal username that day, or perhaps the OpenID site they use has been filtered by a (forced) company proxy.

My suggestion:
Don't implement OpenID on your site(s) as a replacement for a username and password; instead, require a username and password with an option to register an OpenID with the account. (If you want you can say why you require a username and password in your FAQs)

P.S. Also doing this, if your visitor ever changes their OpenID, they have the option do disassociate the current OpenID and associate a new one.

Just wanted to hear some feedback for this idea by my respecting (exaggeration perhaps) community.