So we got millions of people with an OpenID by virtue of their AIM account. Great. Now they just need a place or two to actually use it. —DHH

changeset 6245—Added simple OpenID authentication Rails plugin wrapper for ruby-openid

See also:

• The No Shit Guide To Supporting OpenID In Your Applications—good article on the topic (not using the edge rails, but custom implementation)
• OpenID makes web identities real and appealing—DHH on OpenID
• Restified Bookmarks—ready to go example:

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

• The Rails Open ID Server , developed by EastMedia and VeriSign is a profile management server that can provide full Open ID 1.1 and Yadis services

  svn co http://svn.apache.org/repos/asf/incubator/heraldry/idp/pip/trunk/ pip
  

There is already a lot of OpenID providers:

• MyOpenID ( my identity page )
• Japanese OpenID ( I have already my OpenID.ne.jp registered )
• etc. etc.

Seems Cookie Based Sessions are the New Default in Edge Rails : …Cookie-based sessions are just faster to retrieve and process than hitting the file-system on every request. Plus, I would imagine they scale considerably better as they’re persisted on the client side and have no server-side persistence requirements…

So I made a cookie-based sessions patch agains current Rails (actionpack-1.13.2). Usage (from inside your project):

rake rails:freeze:gems
cd vendor
wget http://zhware.net/code/ruby/ror/session_store-1.13.2.patch
patch -p0 < session_store-1.13.2.patch

I translated Gorou-san’s page for following Edge Rails (original is in japanese) – link to the edgerails page in english . For me the described method seems like a pretty smart way to stay organized, even on the cutting edge.