Close and Go BackBack to Viget

OpenID Authentication Plugin for Rails Now Supports OpenID 2.0

Mark Cornick
Mark Cornick, Web Developer, April 04, 2008 0

A little over a year ago, the open_id_authentication plugin for Rails made its debut, intending to make OpenID authentication simple. And it did, for a while. But, like Rails itself, OpenID is a moving target and the OpenID specification, as well as the ruby-openid library, have both moved on to version 2.0 since then. The API changed enough that the plugin wouldn’t work with the newer library, effectively leaving applications that use it in the OpenID 1.0 world.

This all changed last Thursday. After much deliberation, a new version of open_id_authentication has landed, with support for ruby-openid 2.0.x, and OpenID 2.0 along with it. The upgrade process is pretty painless; a few database tables need attention (the new plugin will generate a migration to take care of those) and you’ll need to tweak any mocks you’re using in your tests/specs (you are using mocks, right?) It took me about half an hour last night. If you’re doing OpenID in your application, or if you think you want to, now’s a great time to take another look at this plugin.

Name:

Email:

URL:

Remember my personal information

Notify me of follow-up comments?

Next entry: Open Source, Take Two.

Previous entry: Git with remotes and SVN

A Development Community for Viget Labs and Beyond

Every team member here at Viget Labs strives to be an innovator. We members of the development team are no different - that's why we're constantly engaging in community discussions and exploring the unknown that is the next generation of open-source web applications.

Viget Is Hiring!

Viget has job openings for Ruby Developers, Interns, and Front-End Developers. Learn More »

Recent Comments

Hi Matt - thanks for the great post! This looks like a very cool way to configure a server - I have one question and excuse my ignorance (Linux newbie): Why do you need to create a “deploy” user at first (as opposed to just using the root account)? Is that actually necessary for running setup_env, or only needed later for regular deployment? Thanks!