binarylogic / authlogic

A simple model based ruby authentication solution.

This URL has Read+Write access

authlogic / README.rdoc
raw normal view history
43e849c6 » binarylogic 2008-11-02 Released v0.10.4 1 = Authlogic
1b98335c » binarylogic 2008-10-24 Initial commit 2
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 3 Authlogic is a clean, simple, and unobtrusive ruby authentication solution.
1b98335c » binarylogic 2008-10-24 Initial commit 4
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 5 A code example can replace a thousand words...
6
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 7 Authlogic introduces a new type of model. You can have as many as you want, and name them whatever you want, just like your other models. In this example, we want to authenticate with the User model, which is inferred by the name:
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 8
9 class UserSession < Authlogic::Session::Base
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 10 # specify configuration here, such as:
11 # logout_on_timeout true
12 # ...many more options in the documentation
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 13 end
14
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 15 Log in with any of the following. Create a UserSessionsController and use it just like your other models:
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 16
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 17 UserSession.create(:login => "bjohnson", :password => "my password", :remember_me => true)
18 session = UserSession.new(:login => "bjohnson", :password => "my password", :remember_me => true); session.save
19 UserSession.create(:openid_identifier => "identifier", :remember_me => true) # requires the authlogic-oid "add on" gem
20 UserSession.create(my_user_object, true) # skip authentication and log the user in directly, the true means "remember me"
21
22 The above handles the entire authentication process for you. It first authenticates, then it sets up the proper session values and cookies to persist the session. Just like you would if you rolled your own authentication solution.
23
24 You can also log out / destroy the session:
25
26 session.destroy
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 27
8c8e079e » binarylogic 2009-04-25 Release v2.0.11 28 After a session has been created, you can persist it across requests. Thus keeping the user logged in:
1b98335c » binarylogic 2008-10-24 Initial commit 29
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 30 session = UserSession.find
af4f7e06 » binarylogic 2009-01-01 Documentation fix for using... 31
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 32 To get all of the nice authentication functionality in your model just do this:
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 33
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 34 class User < ActiveRecord::Base
35 acts_as_authentic do |c|
36 c.my_config_option = my_value
37 end # the configuration block is optional
38 end
9bca67d7 » binarylogic 2008-11-09 Reorganized ORM code and tests 39
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 40 This handles validations, etc. It is also "smart" in the sense that it if a login field is present it will use that to authenticate, if not it will look for an email field, etc. This is all configurable, but for 99% of cases that above is all you will need to do.
41
42 Also, sessions are automatically maintained. You can switch this on and off with configuration, but the following will automatically log a user in after a successful registration:
c5e610ac » binarylogic 2009-04-28 * Extracted Authlogics regu... 43
44 User.create(params[:user])
45
46 This also updates the session when the user changes his/her password.
47
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 48 Authlogic is very flexible, it has a strong public API and a plethora of hooks to allow you to modify behavior and extend it. Check out the helpful links below to dig deeper.
49
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 50 == Helpful links
51
e44e1e35 » binarylogic 2009-06-27 Add gemspec for github 52 * <b>Documentation:</b> http://rdoc.info/projects/binarylogic/authlogic
f638b12b » binarylogic 2009-04-28 * Added the ability to add ... 53 * <b>Repository:</b> http://github.com/binarylogic/authlogic/tree/master
261e8ad4 » binarylogic 2009-05-04 Cleanup how generalize_cred... 54 * <b>Railscasts Screencast:</b> http://railscasts.com/episodes/160-authlogic
f638b12b » binarylogic 2009-04-28 * Added the ability to add ... 55 * <b>Live example with OpenID "add on":</b> http://authlogicexample.binarylogic.com
56 * <b>Live example repository with tutorial in README:</b> http://github.com/binarylogic/authlogic_example/tree/master
57 * <b>Tutorial: Reset passwords with Authlogic the RESTful way:</b> http://www.binarylogic.com/2008/11/16/tutorial-reset-passwords-with-authlogic
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 58 * <b>Bugs / feature suggestions:</b> http://binarylogic.lighthouseapp.com/projects/18752-authlogic
59 * <b>Google group:</b> http://groups.google.com/group/authlogic
60
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 61 <b>Before contacting me directly, please read:</b>
51f7b28b » binarylogic 2009-04-09 * Reset the @password_chang... 62
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 63 If you find a bug or a problem please post it on lighthouse. If you need help with something, please use google groups. I check both regularly and get emails when anything happens, so that is the best place to get help. This also benefits other people in the future with the same questions / problems. Thank you.
ee1f49b2 » binarylogic 2009-04-05 * Use MockCookieJar in test... 64
5c0ac4ff » binarylogic 2009-04-08 * Make password and login f... 65 == Authlogic "add ons"
ee1f49b2 » binarylogic 2009-04-05 * Use MockCookieJar in test... 66
f638b12b » binarylogic 2009-04-28 * Added the ability to add ... 67 * <b>Authlogic OpenID addon:</b> http://github.com/binarylogic/authlogic_openid
68 * <b>Authlogic LDAP addon:</b> http://github.com/binarylogic/authlogic_ldap
bcb0d4af » binarylogic 2009-06-10 * Stop using errors.on(key)... 69 * <b>Authlogic Facebook Connect:</b> http://github.com/kalasjocke/authlogic_facebook_connect
639a0355 » jrallison 2009-06-27 Signed-off-by: Ben Johnson ... 70 * <b>Authlogic OAuth (Twitter):</b> http://github.com/jrallison/authlogic_oauth
ee1f49b2 » binarylogic 2009-04-05 * Use MockCookieJar in test... 71
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 72 If you create one of your own, please let me know about it so I can add it to this list. Or just fork the project, add your link, and send me a pull request.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 73
f638b12b » binarylogic 2009-04-28 * Added the ability to add ... 74 == Session bugs (please read if you are having issues with logging in / out)
75
76 Apparently there is a bug with apache / passenger for v2.1.X with sessions not working properly. This is most likely your problem if you are having trouble logging in / out. This is *not* an Authlogic issue. This can be solved by updating passener or using an alternative session store solution, such as active record store.
77
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 78 == Documentation explanation
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 79
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 80 You can find anything you want about Authlogic in the {documentation}[http://authlogic.rubyforge.org], all that you need to do is understand the basic design behind it.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 81
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 82 That being said, there are 2 models involved during authentication. Your Authlogic model and your ActiveRecord model:
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 83
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 84 1. <b>Authlogic::Session</b>, your session models that extend Authlogic::Session::Base.
85 2. <b>Authlogic::ActsAsAuthentic</b>, which adds in functionality to your ActiveRecord model when you call acts_as_authentic.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 86
0823cc7d » binarylogic 2009-04-20 Releast v2.0.10 87 Each of the above has its various sub modules that contain common logic. The sub modules are responsible for including *everything* related to it: configuration, class methods, instance methods, etc.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 88
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 89 For example, if you want to timeout users after a certain period of inactivity, you would look in <b>Authlogic::Session::Timeout</b>. To help you out, I listed the following publicly relevant modules with short descriptions. For the sake of brevity, there are more modules than listed here, the ones not listed are more for internal use, but you can easily read up on them in the {documentation}[http://authlogic.rubyforge.org].
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 90
c355cdd2 » binarylogic 2009-03-21 Some documentation clean up 91 === Authlogic::ActsAsAuthentic sub modules
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 92
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 93 These modules are for the ActiveRecord side of things, the models that call acts_as_authentic.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 94
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 95 * <b>Authlogic::ActsAsAuthentic::Base</b> - Provides the acts_as_authentic class method and includes all of the submodules.
96 * <b>Authlogic::ActsAsAuthentic::Email</b> - Handles everything related to the email field.
97 * <b>Authlogic::ActsAsAuthentic::LoggedInStatus</b> - Provides handy named scopes and methods for determining if the user is logged in or out.
98 * <b>Authlogic::ActsAsAuthentic::Login</b> - Handles everything related to the login field.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 99 * <b>Authlogic::ActsAsAuthentic::MagicColumns</b> - Handles everything related to the "magic" fields: login_count, failed_login_count, last_request_at, etc.
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 100 * <b>Authlogic::ActsAsAuthentic::Password</b> - This one is important. It handles encrypting your password, salting it, etc. It also has support for transitioning password algorithms.
101 * <b>Authlogic::ActsAsAuthentic::PerishableToken</b> - Handles maintaining the perishable token field, also provides a class level method for finding record using the token.
102 * <b>Authlogic::ActsAsAuthentic::PersistenceToken</b> - Handles maintaining the persistence token. This is the token stored in cookies and sessions to persist the users session.
103 * <b>Authlogic::ActsAsAuthentic::RestfulAuthentication</b> - Provides configuration options to easily migrate from the restful_authentication plugin.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 104 * <b>Authlogic::ActsAsAuthentic::SessionMaintenance</b> - Handles automatic session maintenance. EX: a new user registers, automatically log them in. Or a user changes their password, update their session.
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 105 * <b>Authlogic::ActsAsAuthentic::SingleAccessToken</b> - Handles maintaining the single access token.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 106 * <b>Authlogic::ActsAsAuthentic::ValidationsScope</b> - Allows you to scope all validations, etc. Just like the :scope option for validates_uniqueness_of
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 107
c355cdd2 » binarylogic 2009-03-21 Some documentation clean up 108 === Authlogic::Session sub modules
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 109
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 110 These modules are for the models that extend Authlogic::Session::Base.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 111
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 112 * <b>Authlogic::Session::BruteForceProtection</b> - Disables accounts after a certain number of consecutive failed logins attempted.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 113 * <b>Authlogic::Session::Callbacks</b> - Your tools to extend, change, or add onto Authlogic. Lets you hook in and do just about anything you want. Start here if you want to write a plugin or add-on for Authlogic
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 114 * <b>Authlogic::Session::Cookies</b> - Authentication via cookies.
115 * <b>Authlogic::Session::Existence</b> - Creating, saving, and destroying objects.
116 * <b>Authlogic::Session::HttpAuth</b> - Authentication via basic HTTP authentication.
117 * <b>Authlogic::Session::Id</b> - Allows sessions to be separated by an id, letting you have multiple sessions for a single user.
118 * <b>Authlogic::Session::MagicColumns</b> - Maintains "magic" database columns, similar to created_at and updated_at for ActiveRecord.
119 * <b>Authlogic::Session::MagicStates</b> - Automatically validates based on the records states: active?, approved?, and confirmed?. If those methods exist for the record.
120 * <b>Authlogic::Session::Params</b> - Authentication via params, aka single access token.
121 * <b>Authlogic::Session::Password</b> - Authentication via a traditional username and password.
122 * <b>Authlogic::Session::Persistence</b> - Persisting sessions / finding sessions.
123 * <b>Authlogic::Session::Session</b> - Authentication via the session, the controller session that is.
124 * <b>Authlogic::Session::Timeout</b> - Automatically logging out after a certain period of inactivity.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 125 * <b>Authlogic::Session::UnauthorizedRecord</b> - Handles authentication by passing an ActiveRecord object directly.
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 126 * <b>Authlogic::Session::Validation</b> - Validation / errors.
21554776 » binarylogic 2008-10-28 Updated readme 127
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 128 === Miscellaneous modules
43e849c6 » binarylogic 2008-11-02 Released v0.10.4 129
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 130 Miscellaneous modules that shared across the authentication process and are more "utility" modules and classes.
78f5befa » binarylogic 2009-03-22 Restructure configuration f... 131
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 132 * <b>Authlogic::AuthenticatesMany</b> - Responsible for allowing you to scope sessions to a parent record. Similar to a has_many and belongs_to relationship. This lets you do the same thing with sessions.
133 * <b>Authlogic::CryptoProviders</b> - Contains various encryption algorithms that Authlogic uses, allowing you to choose your encryption method.
134 * <b>Authlogic::I18n</b> - Acts JUST LIKE the rails I18n library, and provides internationalization to Authlogic.
135 * <b>Authlogic::Random</b> - A simple class to generate random tokens.
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 136 * <b>Authlogic::Regex</b> - Contains regular expressions used in Authlogic. Such as those to validate the format of the log or email.
d1bf2d1a » binarylogic 2009-04-20 Fix some RDOC syntax mistakes 137 * <b>Authlogic::TestCase</b> - Various helper methods for testing frameworks to help you test your code.
138 * <b>Authlogic::Version</b> - A handy class for determine the version of Authlogic in a number of ways.
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 139
0823cc7d » binarylogic 2009-04-20 Releast v2.0.10 140 == Quick Rails example
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 141
142 What if creating sessions worked like an ORM library on the surface...
e77ca8a3 » binarylogic 2008-10-25 Updated readme 143
4b1f8faf » binarylogic 2008-10-28 User column_names instead o... 144 UserSession.create(params[:user_session])
e77ca8a3 » binarylogic 2008-10-25 Updated readme 145
34b225cf » binarylogic 2008-10-25 Updated readme 146 What if your user sessions controller could look just like your other controllers...
1b98335c » binarylogic 2008-10-24 Initial commit 147
148 class UserSessionsController < ApplicationController
149 def new
150 @user_session = UserSession.new
151 end
152
153 def create
154 @user_session = UserSession.new(params[:user_session])
35f14baf » binarylogic 2008-10-27 Released v0.10.0 155 if @user_session.save
c93bec2d » binarylogic 2008-10-24 Changed scope to id 156 redirect_to account_url
1b98335c » binarylogic 2008-10-24 Initial commit 157 else
158 render :action => :new
159 end
160 end
161
162 def destroy
ebdebfa9 » binarylogic 2008-11-13 Released v1.1.1 163 current_user_session.destroy
4caccd0b » binarylogic 2008-11-19 Released 1.2.1 164 redirect_to new_user_session_url
1b98335c » binarylogic 2008-10-24 Initial commit 165 end
166 end
167
605162d3 » binarylogic 2009-03-20 Release v2.0 RC1 168 As you can see, this fits nicely into the RESTful development pattern. What about the view...
1b98335c » binarylogic 2008-10-24 Initial commit 169
170 <% form_for @user_session do |f| %>
791f700e » binarylogic 2008-11-05 Released v1.0.0 (see change... 171 <%= f.error_messages %>
1b98335c » binarylogic 2008-10-24 Initial commit 172 <%= f.label :login %><br />
173 <%= f.text_field :login %><br />
174 <br />
175 <%= f.label :password %><br />
176 <%= f.password_field :password %><br />
177 <br />
178 <%= f.submit "Login" %>
179 <% end %>
180
34b225cf » binarylogic 2008-10-25 Updated readme 181 Or how about persisting the session...
1b98335c » binarylogic 2008-10-24 Initial commit 182
183 class ApplicationController
ebdebfa9 » binarylogic 2008-11-13 Released v1.1.1 184 helper_method :current_user_session, :current_user
1b98335c » binarylogic 2008-10-24 Initial commit 185
dbd8b8f5 » binarylogic 2008-11-16 Release v1.2.0 Comment 186 private
ebdebfa9 » binarylogic 2008-11-13 Released v1.1.1 187 def current_user_session
188 return @current_user_session if defined?(@current_user_session)
189 @current_user_session = UserSession.find
190 end
191
69f2c2b6 » binarylogic 2009-01-08 Add a logout_on_timeout con... Comment 192 def current_user
ebdebfa9 » binarylogic 2008-11-13 Released v1.1.1 193 return @current_user if defined?(@current_user)
194 @current_user = current_user_session && current_user_session.user
1b98335c » binarylogic 2008-10-24 Initial commit 195 end
196 end
197
0f38680b » binarylogic 2009-04-17 Update README and move setu... 198 == Install & Use
c355cdd2 » binarylogic 2009-03-21 Some documentation clean up 199
93a47874 » binarylogic 2008-11-09 Added Sha1 crypto provider ... 200 Install the gem / plugin (recommended)
1b98335c » binarylogic 2008-10-24 Initial commit 201
58d726d1 » binarylogic 2009-06-27 Update the readme 202 From rubyforge:
203
43e849c6 » binarylogic 2008-11-02 Released v0.10.4 204 $ sudo gem install authlogic
1b98335c » binarylogic 2008-10-24 Initial commit 205
53834196 » binarylogic 2009-07-01 Use mb_chars when downcasin... 206 Or from github:
58d726d1 » binarylogic 2009-06-27 Update the readme 207
208 $ sudo gem install binarylogic-authlogic
209
e44e1e35 » binarylogic 2009-06-27 Add gemspec for github 210 Now just add the gem dependency in your projects configuration.
93a47874 » binarylogic 2008-11-09 Added Sha1 crypto provider ... 211
53834196 » binarylogic 2009-07-01 Use mb_chars when downcasin... 212 Or you can install this as a plugin:
1b98335c » binarylogic 2008-10-24 Initial commit 213
43e849c6 » binarylogic 2008-11-02 Released v0.10.4 214 script/plugin install git://github.com/binarylogic/authlogic.git
1b98335c » binarylogic 2008-10-24 Initial commit 215
0823cc7d » binarylogic 2009-04-20 Releast v2.0.10 216 == Detailed Setup Tutorial
35f14baf » binarylogic 2008-10-27 Released v0.10.0 217
0823cc7d » binarylogic 2009-04-20 Releast v2.0.10 218 See the {authlogic example}[http://github.com/binarylogic/authlogic_example/tree/master] for a detailed setup tutorial. I did this because not only do you have a tutorial to go by, but you have an example app that uses the same tutorial, so you can play around with with the code. If you have problems you can compare the code to see what you are doing differently.
40267c6c » binarylogic 2009-04-16 Update README with more tho... 219
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 220 == Testing
221
222 I think one of the best aspects of Authlogic is testing. For one, it cuts out <b>a lot</b> of redundant tests in your applications because Authlogic is already thoroughly tested for you. It doesn't include a bunch of tests into your application, because it comes tested, just like any other library.
223
224 For example, think about ActiveRecord. You don't test the internals of ActiveRecord, because the creators of ActiveRecord have already tested the internals for you. It wouldn't make sense for ActiveRecord to copy it's hundreds of tests into your applications. The same concept applies to Authlogic. You only need to test code you write that is specific to your application, just like everything else in your application.
225
8c8e079e » binarylogic 2009-04-25 Release v2.0.11 226 That being said, testing your code that uses Authlogic is easy. Since everyone uses different testing suites, I created a helpful module called Authlogic::TestCase, which is basically a set of tools for testing code using Authlogic. I explain testing Authlogic thoroughly in the {Authlogic::TestCase section of the documentation}[http://authlogic.rubyforge.org/classes/Authlogic/TestCase.html]. It should answer any questions you have in regards to testing Authlogic.
d23f64e9 » binarylogic 2009-04-25 Add some comments on testin... 227
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 228 == Tell me quickly how Authlogic works
21554776 » binarylogic 2008-10-28 Updated readme 229
b3657216 » binarylogic 2009-05-02 Fix typo in mock request 230 Interested in how all of this all works? Think about an ActiveRecord model. A database connection must be established before you can use it. In the case of Authlogic, a controller connection must be established before you can use it. It uses that controller connection to modify cookies, the current session, login with HTTP basic, etc. It connects to the controller through a before filter that is automatically set in your controller which lets Authlogic know about the current controller object. Then Authlogic leverages that to do everything, it's a pretty simple design. Nothing crazy going on, Authlogic is just leveraging the tools your framework provides in the controller object.
21554776 » binarylogic 2008-10-28 Updated readme 231
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 232 == What sets Authlogic apart and why I created it
21554776 » binarylogic 2008-10-28 Updated readme 233
8c8e079e » binarylogic 2009-04-25 Release v2.0.11 234 What inspired me to create Authlogic was the messiness of the current authentication solutions. Put simply, they just didn't feel right, because the logic was not organized properly. As you may know, a common misconception with the MVC design pattern is that the model "M" is only for data access logic, which is wrong. A model is a place for domain logic. This is why the RESTful design pattern and the current authentication solutions don't play nice. Authlogic solves this by placing the session maintenance logic into its own domain (aka "model"). Moving session maintenance into its own domain has its benefits:
ec0eb78e » binarylogic 2008-10-31 Updated readme 235
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 236 1. <b>It's cleaner.</b> There are no generators in Authlogic. Authlogic provides a class that you can use, it's plain and simple ruby. More importantly, the code in your app is code you write, written the way you want, nice and clean. It's code that should be in your app and is specific to your app, not a redundant authentication pattern.
2af08aba » binarylogic 2009-04-20 Add a quick model explanati... 237 2. <b>Easier to stay up-to-date.</b> To make my point, take a look at the commits to any other authentication solution, then look at the {commits for authlogic}[http://github.com/binarylogic/authlogic/commits/master]. How many commits could you easily start using if you already had an app using that solution? With an alternate solution, very few, if any. All of those cool new features and bug fixes are going to have be manually added or wait for your next application. Which is the main reason a generator is not suitable as an authentication solution. With Authlogic you can start using the latest code with a simple update of a gem. No generators, no mess.
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 238 3. <b>It ties everything together on the domain level.</b> Take a new user registration for example, no reason to manually log the user in, authlogic handles this for you via callbacks. The same applies to a user changing their password. Authlogic handles maintaining the session for you.
239 4. <b>No redundant tests.</b> Because Authlogic doesn't use generators, #1 also applies to tests. Authlogic is *thoroughly* tested for you. You don't go and test the internals of ActiveRecord in each of your apps do you? So why do the same for Authlogic? Your application tests should be for application specific code. Get rid of the noise and make your tests focused and concise, no reason to copy tests from app to app.
4732d057 » binarylogic 2009-04-25 Add note about rails cookie... 240 5. <b>Framework agnostic</b>. Authlogic can be used in *any* ruby framework you want: Rails, Merb, Sinatra, Mack, your own framework, whatever. It's not tied down to Rails. It does this by abstracting itself from these framework's controllers by using a controller adapter. Thanks to {Rack}[http://rack.rubyforge.org/], there is a defined standard for controller structure, and that's what Authlogic's abstract adapter follows. So if your controller follows the rack standards, you don't need to do anything. Any place it deviates from this is solved by a simple adapter for your framework that closes these gaps. For an example, checkout the Authlogic::ControllerAdapters::MerbAdapter.
ec82400e » binarylogic 2009-04-20 Make the README simpler and... 241 5. <b>You are not restricted to a single session.</b> Think about Apple's me.com, where they need you to authenticate a second time before changing your billing information. Why not just create a second session for this? It works just like your initial session. Then your billing controller can require an "ultra secure" session.
242 6. <b>Easily extendable.</b> One of the distinct advantages of using a library is the ability to use it's API, assuming it has one. Authlogic has an *excellent* public API, meaning it can easily be extended and grow beyond the core library. Checkout the "add ons" list above to see what I mean.
ec0eb78e » binarylogic 2008-10-31 Updated readme 243
1b98335c » binarylogic 2008-10-24 Initial commit 244
0823cc7d » binarylogic 2009-04-20 Releast v2.0.10 245 Copyright (c) 2009 {Ben Johnson of Binary Logic}[http://www.binarylogic.com], released under the MIT license