http://www.chickenwingsw.com/scratches/programming/openid-is-useless Developing ideas on developing. Fri, 20 May 2011 10:39:44 +0000 hourly 1 http://wordpress.org/?v=3.1.2 http://www.chickenwingsw.com/scratches/programming/openid-is-useless/comment-page-1#comment-21228 Mike Sat, 29 Jan 2011 17:51:03 +0000 http://www.chickenwingsoftware.com/scratches/programming/openid-is-useless#comment-21228 Love Scopa, btw. <br /><br /> Anyway, not sure when this article was written, but janrain's RPXnow completely eliminates the barriers to OpenID. <br /><br /> I had similar issues trying to implement on my own site. My biggest one, though, was the barrier to entry because the user had to know what his/her 'uri' was! <br /><br /> I currently use the free version of RPXnow, where the only real drawback is that the redirect is to .rpxnow.com instead of my own domain, which may make some people feel uneasy. <br /><br /> From what I've seen from your site, I imagine that you could probably write your own framework to simplify the experience for users and get back the info that you need (that they allow you to see). <br /><br /> One more comment about getting "info" on the users. <br /> While it would be great for users to be able to fill in their personal info (name) with their openid provider and then share that with the openid consumers, many people would feel more comfortable simply authenticating and filling in their details separately for each site. <br /><br /> Basically, to use your sites with openid, you would still need to register, but use an openid instead of creating a new username/password on your site. <br /><br /> You still need to have a user db, but don't have to deal with passwords, etc. <br /><br /> You could still even allow people to use the site unregistered, and just enter a temporary name and not store any info about him/her.<br />
Anyway, not sure when this article was written, but janrain's RPXnow completely eliminates the barriers to OpenID.

I had similar issues trying to implement on my own site. My biggest one, though, was the barrier to entry because the user had to know what his/her 'uri' was!

I currently use the free version of RPXnow, where the only real drawback is that the redirect is to .rpxnow.com instead of my own domain, which may make some people feel uneasy.

From what I've seen from your site, I imagine that you could probably write your own framework to simplify the experience for users and get back the info that you need (that they allow you to see).

One more comment about getting "info" on the users.
While it would be great for users to be able to fill in their personal info (name) with their openid provider and then share that with the openid consumers, many people would feel more comfortable simply authenticating and filling in their details separately for each site.

Basically, to use your sites with openid, you would still need to register, but use an openid instead of creating a new username/password on your site.

You still need to have a user db, but don't have to deal with passwords, etc.

You could still even allow people to use the site unregistered, and just enter a temporary name and not store any info about him/her.
]]>