Ruby on Rails
Authentication (Version #182)

This article is part of the confusing world of Authentication in Rails. Feel free to help.

There are about over nine thousand ways to do authentication, but Acts_as_authenticated stands out as one of the more sane solutions.

The gazillion different authentication systems

  • Crypted Authentication Plugin – A simple but effective encrypted password plugin for Rails. It deals with the encryption of a clear-text password using a randomly generated salt, and authentication. It does not try to do too much – it makes no major assumptions about your domain and only requires a small change to your schema to implement. It is extracted from code used on several projects and contains a full BDD-style test suite.
  • OpenID – A decentralized URL based identity system. An OpenID is simply a URL, and all the OpenID specification does is describe a way to securely prove that the user owns that URL. Particulary useful where SSO is needed.
  • LoginSugar – An improved version of SaltedHashLoginGenerator.
  • Auth_generator – A generator by penso. There is a video and information how to install it. It supports different ways to crypt password (MD5, SHA, SHA+login as a salt), all the usual features (send email for forgotten password, create account, resent confirmation, etc).
  • Goldberg – A more comprehensive security solution that also includes role-based access control, site navigation, a simple CMS and a management interface.

Even more? Yes!

Now that you’ve seen what libraries/plugins/engines/whatever exist to confuse your when choosing your authentication system, why not get confused even more?

This article is part of the confusing world of Authentication in Rails. Feel free to help.

There are about over nine thousand ways to do authentication, but Acts_as_authenticated stands out as one of the more sane solutions.

The gazillion different authentication systems

  • Crypted Authentication Plugin – A simple but effective encrypted password plugin for Rails. It deals with the encryption of a clear-text password using a randomly generated salt, and authentication. It does not try to do too much – it makes no major assumptions about your domain and only requires a small change to your schema to implement. It is extracted from code used on several projects and contains a full BDD-style test suite.
  • OpenID – A decentralized URL based identity system. An OpenID is simply a URL, and all the OpenID specification does is describe a way to securely prove that the user owns that URL. Particulary useful where SSO is needed.
  • LoginSugar – An improved version of SaltedHashLoginGenerator.
  • Auth_generator – A generator by penso. There is a video and information how to install it. It supports different ways to crypt password (MD5, SHA, SHA+login as a salt), all the usual features (send email for forgotten password, create account, resent confirmation, etc).
  • Goldberg – A more comprehensive security solution that also includes role-based access control, site navigation, a simple CMS and a management interface.

Even more? Yes!

Now that you’ve seen what libraries/plugins/engines/whatever exist to confuse your when choosing your authentication system, why not get confused even more?