Jigyasa Makkar
e2030a740d
Fixed a bug in lockable wherein when a user tries to login with correct password after being locked,
...
failed attempts count gets reset. When the user tries to login with an incorrect password next,
the message shown is for invalid password instead of locked account since this check
depended mainly on failed attempts count.
2011-12-29 23:57:39 +05:30
SixArm
2a5669967f
Change test email addresses to ues RFC 2606 reserved domain example.com
2011-04-18 15:59:13 +08:00
José Valim
edee511cd1
Rename active? to active_for_authentication?
2011-03-25 15:40:46 +01:00
Vinicius Baggio
0cc900e7cf
Reset lock attempts count when lock is expired. Closes #825
2011-02-25 17:59:27 -03:00
Nico Ritsche
f06bed279a
corrected 'an user' to 'a user' in comments and docs
2011-02-06 23:46:49 +08:00
Richard Aday
88d4aca2c4
Adding tests for reset_password_keys and unlock_keys
2010-12-30 03:11:03 +08:00
José Valim
8f20b13f84
By default, just require e-mail on recover and lockable.
2010-12-28 23:00:23 +01:00
José Valim
5429f940e7
Refactor code related with authentication keys on password recovery and account unlocking, closes #396 .
2010-09-21 12:05:17 +02:00
RStankov
fb86f772e7
make User#send_unlock_instructions to require all authentication_keys
...
Signed-off-by: José Valim <jose.valim@gmail.com>
2010-09-21 11:46:57 +02:00
José Valim
870912d458
beta 4 works, yay.
2010-06-09 01:27:38 +02:00
José Valim
c07b5ae858
:activatable is included by default in your models. If you are building a strategy for devise, you now need to call validate(resource), since Devise has now a default API to validate resources before and after signing them in. You can still use other Warden::Strategies with Devise, but they won't work with a few modules like unlockable (they never did, but now we have a single point to make it work).
2010-04-06 16:34:22 +02:00
José Valim
6cc32db2dd
Add lock_strategy.
2010-03-31 11:54:11 +02:00
José Valim
7d14f0bbb9
Allow several authentications to share a common path.
2010-03-29 23:44:47 +02:00
Jacques Crocker
6d31e368bf
Use persisted? instead of new_record?
...
In order to be more ActiveModel compliant, lets use persisted? whereever we can. Particularly for datamapper, new_record? causes api warnings. Better to stick to the ActiveModel api I think.
2010-03-28 20:53:13 -07:00
José Valim
2a082f3e4c
Fix some unlockable bugs.
2010-03-28 23:09:28 +02:00
José Valim
ca4e09390e
Compatibility with Ruby 1.9.1 and 1.9.2.
2010-03-26 11:27:19 +01:00
José Valim
ac742e3271
Clean up lockable and class methods API.
2010-03-10 16:13:54 +01:00
José Valim
e6e66481b8
Got all tests in test/models and failure app ones passing. 369 tests, 805 assertions, 13 failures, 2 errors.
2010-02-16 17:00:36 +01:00
Carlos Antonio da Silva
21359fb433
Refactoring a bit models and lockable. Also remove devise :all deprecation.
2010-02-04 20:09:53 -02:00
Marcelo Silveira
d2fa737aa0
introducing lockable implementation
2010-01-01 17:57:35 -02:00
