Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jul 23, 2009
  1. @reinh @binarylogic

    Fix misplaced apostrophe in README

    reinh authored binarylogic committed
    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>
Commits on Jul 22, 2009
  1. @crankharder @binarylogic

    added support for a custom generalized error message

    crankharder authored binarylogic committed
    Added docs
    
    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>
Commits on Jul 21, 2009
  1. @shadowmaru @binarylogic

    Changed model_class to described_type for compatibility with Shoulda …

    shadowmaru authored binarylogic committed
    …2.10.2
    
    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>
Commits on Jul 13, 2009
  1. @binarylogic

    * Add a model_name class method for Authlogic::Session for rails 3 co…

    binarylogic authored
    …mpatibility. Will be using ActiveModel eventually, but this should be a quick fix.
Commits on Jul 10, 2009
  1. @binarylogic
Commits on Jul 4, 2009
  1. @binarylogic
  2. @binarylogic

    Update changelog

    binarylogic authored
  3. @binarylogic

    Version bump to 2.1.1

    binarylogic authored
  4. @binarylogic
Commits on Jul 2, 2009
  1. @binarylogic
  2. @binarylogic
  3. @binarylogic
Commits on Jun 30, 2009
  1. @mynyml @binarylogic

    Fix Rails version check.

    mynyml authored binarylogic committed
    Previous check would fail with Rails >= 3.0
    
    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>
Commits on Jun 27, 2009
  1. @binarylogic

    Add gemspec for github

    binarylogic authored
  2. @binarylogic

    Update the readme

    binarylogic authored
  3. @binarylogic
  4. @binarylogic
  5. @binarylogic

    Version bump to 2.1.0

    binarylogic authored
  6. @binarylogic

    Version bump to 0.0.0

    binarylogic authored
  7. @binarylogic

    Version bump to 1.0.0

    binarylogic authored
  8. @binarylogic

    Version bump to 0.0.0

    binarylogic authored
  9. @binarylogic

    Version bump to 0.1.0

    binarylogic authored
  10. @binarylogic

    Version bump to 0.0.0

    binarylogic authored
  11. @jrallison @binarylogic

    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>

    jrallison authored binarylogic committed
Commits on Jun 24, 2009
  1. @binarylogic
  2. @binarylogic

    * Fixed bug when using act_like_restful_authentication and setting pa…

    binarylogic authored
    …sswords, needed to add a 2nd parameter to tell if to check against the database or not.
Commits on Jun 20, 2009
  1. @hardbap @binarylogic

    Added find_using_perishable_token! to raise AR::RecordNotFound if no …

    hardbap authored binarylogic committed
    …record matches query.
    
    Signed-off-by: Ben Johnson <bjohnson@binarylogic.com>
Commits on Jun 13, 2009
  1. @binarylogic

    Release v2.0.14

    binarylogic authored
Commits on Jun 12, 2009
  1. @binarylogic

    * Use valid_password? for the method name to validate a password inst…

    binarylogic authored
    …ead of valid_#{password_field}?.
Commits on Jun 10, 2009
  1. @binarylogic
Commits on Jun 3, 2009
  1. @binarylogic

    Added db_setup? method to avoid errors during rake tasks where the db…

    binarylogic authored
    … might not be set up. Ex: migrations
  2. @binarylogic
Commits on May 28, 2009
  1. @binarylogic
  2. @binarylogic

    * Fixed issue with using brute force protection AND generalize_creden…

    binarylogic authored
    …tials_error_messages. Brute force protection was looking to see if there were password errors, which generalize_credentials_error_messages was obfuscating. This is all fixed now though thanks to a handy article on Microsoft ( http://support.microsoft.com/kb/168702 ), method #2, it works every time.
  3. @binarylogic

    * Fixed issue with using brute force protection AND generalize_creden…

    binarylogic authored
    …tials_error_messages. Brute force protection was looking to see if there were password errors, which generalize_credentials_error_messages was obfuscating. This is all fixed now though thanks to a handy article on Microsoft (http://support.microsoft.com/kb/168702), method #2, it works every time.
Something went wrong with that request. Please try again.