Devise Versions Save

Flexible authentication solution for Rails with Warden.

5 years ago

5 years ago

5 years ago

6 years ago

6 years ago

6 years ago

6 years ago

8 years ago

bug fixes
- Fix password reset for records where confirmation_required? is disabled and confirmation_sent_at is nil. (by @andygeers)
- Allow resources with no email field to be recoverable (and do not clear the reset password token if the model was already persisted). (by @seddy, @stanhu)
enhancements
- Upon setting Devise.send_password_change_notification = true a user will receive notification when their password has been changed.

8 years ago

enhancements
- Perform case insensitive basic authorization matching
bug fixes
- Do not use digests for password confirmation token
- Fix infinite redirect in Rails 4.2 authenticated routes
- Autoload Devise::Encryptor to avoid errors on thread-safe mode
deprecations
- config.expire_auth_token_on_timeout was removed

9 years ago

enhancements
- Support added for Rails 4.2. Devise now depends on the responders gem due the extraction of the respond_with API from Rails. (by @lucasmazza)
- The Simple Form templates follow the same change from 3.3.0 by using Log in and adding a hint about the minimum password length when validatable is enabled. (by @aried3r)
- Controller generator added as devise:controllers SCOPE. You can use the -c flag to pick which controllers (unlocks, confirmations, etc) you want to generate. (by @Chun-Yang)
- Removed the hardcoded references for "email" in the flash messages. If you are using different attributes as the authentication_keys they will be interpolated in the messages instead. (by @timoschilling)
bug fix
- Fixed a regression where the devise generator would fail with a ConnectionNotEstablished exception when executed inside a mountable engine. (by @lucasmazza)
- Ensure to return symbols in find_scope! fixing a previous regression from 3.3.0 (by @micat)
- Ensure all causes of failed login have the same error message (by @pjungwir)
- The last_attempt_warning now takes effect when generating the unauthenticated message for your users. To keep the current behavior, this flag is now true by default. (by @lucasmazza)