restful-authentication

Well, here's the initial commit of RESTful Authentication library from 2006: https://github.com/technoweenie/restful-authentication/commi.... FYI, still using in production like a charm!

It was a part of the restful authentication plugin I originally used to set it up [1] :) For this app its necessary because I allow users to share the timelines they create and I display their user names on the shared timelines. Your train of thought is good though. [1] https://github.com/technoweenie/restful-authentication

There are various Rails plugins that take care of most of this stuff. I've had great success with restful_authentication (http://github.com/technoweenie/restful-authentication)

Interestingly, there's a new branch (http://github.com/technoweenie/restful-authentication/tree/m...) of Restful Authentication (labeled "Experimental Branch" in the README for the main branch) that backs away from the code generation approach of the current and previous versions of Restful Auth. To quote from readme in the modular branch of Restful Authentication: "The plugin now generates much less app-space code: the controllers are super skinny now, and if any security flaws are discovered it should be less painfulto stay current." I applaud their new direction, but IMHO the fact that this is their new direction validates my point that their old direction was just plain wrong. Code generation is little different than "cut and paste" programming.

Hashed, salted. The email address isn't checked, so if you really don't want to give it out, put in garbage with an '@'. http://github.com/technoweenie/restful-authentication/tree/m...