Comments on: Why the lack of OpenID-enabled Rails apps? http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/ small batches of software goodness Mon, 08 Sep 2008 13:38:26 +0000 http://wordpress.org/?v=2.5.1 By: Tony http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-17848 Tony Sat, 29 Sep 2007 20:49:55 +0000 http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-17848 Here are a couple of rails apps that use OID: http://svvarm.com http://votemonkey.com Although both are useful without any authentication, the community aspects of these applications increases by setting up a user - which may be based on your open id. Enjoy. Here are a couple of rails apps that use OID:

http://svvarm.com
http://votemonkey.com

Although both are useful without any authentication, the community aspects of these applications increases by setting up a user - which may be based on your open id.

Enjoy.

]]> By: Adam Marsh http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-955 Adam Marsh Tue, 06 Mar 2007 21:29:12 +0000 http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-955 I think that the hassles of integrating and maintaining any library, whether on Rails or any other framework, is a big reason why there aren't more OpenID-enabled web applications. Most folks want to focus on their apps, and this identity stuff isn't super easy to deal with. I posted on an idea that I think might be able to address this and also the issues of drop-in authentication and continued username / password use you mention. Check it out: http://www.econometa.com/archives/51 Do you think this kind of tool would make it easier for developers to support OpenID? I think that the hassles of integrating and maintaining any library, whether on Rails or any other framework, is a big reason why there aren’t more OpenID-enabled web applications. Most folks want to focus on their apps, and this identity stuff isn’t super easy to deal with.

I posted on an idea that I think might be able to address this and also the issues of drop-in authentication and continued username / password use you mention. Check it out:

http://www.econometa.com/archives/51

Do you think this kind of tool would make it easier for developers to support OpenID?

]]> By: Bernie Thompson http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-679 Bernie Thompson Wed, 21 Feb 2007 20:26:32 +0000 http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-679 Thanks, Matt. Thanks for all the great Eastmedia Ruby-OpenID work! Some of the trouble I had with the bookmarks sample app was because the trunk (at least up to Revision 11) used open_id_fields['openid.sreg.nickname'] in the complete() method, instead of open_id_fields['nickname']. I didn't track down when ruby-openid made this (breaking?) change to shorten the sreg keys, but the new restified version you linked to does use open_id_fields['nickname']. This is a great sample to iron out, because it does combine pwd & openid auth and you all have the experience to turn it into an effective plugin. Thanks!! Thanks, Matt. Thanks for all the great Eastmedia Ruby-OpenID work!

Some of the trouble I had with the bookmarks sample app was because the trunk (at least up to Revision 11) used open_id_fields['openid.sreg.nickname'] in the complete() method, instead of open_id_fields['nickname']. I didn’t track down when ruby-openid made this (breaking?) change to shorten the sreg keys, but the new restified version you linked to does use open_id_fields['nickname'].

This is a great sample to iron out, because it does combine pwd & openid auth and you all have the experience to turn it into an effective plugin. Thanks!!

]]> By: Matt Pelletier http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-675 Matt Pelletier Wed, 21 Feb 2007 14:02:16 +0000 http://leancode.com/2007/02/20/why-the-lack-of-openid-enabled-rails-apps/#comment-675 Bernie, Hi. I'm glad you got a chance to see the Bookmarks app. We have recently updated it for Rails 1.2.2, so it is based on restful_authentication and is fully RESTful (at least according to the Rails interpretation of REST). We completely agree that developing an idiom for a dual-login system that offers the same simplicity and convenience of the acts_as_authenticated / restful_authentication plugins is difficult. We hope the Bookmarks app can help demonstrate what such a setup might look like. Please take a look at the current branch of the RESTified app, which works out of the box. We would love to hear any thoughts and suggestions about how to simplify it without getting in the way of app-specific requirements. http://svn.eastmedia.com/svn/bantay/projects/bookmarks/branches/restified/ We're cleaning up the tests and a few minor issues, but it works as expected. We'll be pushing some changes into a restful version of the consumer plugin soon. See docs/README_FOR_APP. Good luck! Thanks, Matt Bernie,

Hi. I’m glad you got a chance to see the Bookmarks app. We have recently updated it for Rails 1.2.2, so it is based on restful_authentication and is fully RESTful (at least according to the Rails interpretation of REST). We completely agree that developing an idiom for a dual-login system that offers the same simplicity and convenience of the acts_as_authenticated / restful_authentication plugins is difficult. We hope the Bookmarks app can help demonstrate what such a setup might look like.

Please take a look at the current branch of the RESTified app, which works out of the box. We would love to hear any thoughts and suggestions about how to simplify it without getting in the way of app-specific requirements.

http://svn.eastmedia.com/svn/bantay/projects/bookmarks/branches/restified/

We’re cleaning up the tests and a few minor issues, but it works as expected. We’ll be pushing some changes into a restful version of the consumer plugin soon. See docs/README_FOR_APP.

Good luck!

Thanks,
Matt

]]>