| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Since we have `has_secure_token`, it is too confusing to use `_token`
suffix with `has_secure_password`.
Context https://github.com/rails/rails/pull/33307#discussion_r200807185
|
|\
| |
| |
| | |
Allow configurable attribute name on `#has_secure_password`
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
existing `#has_secure_password`. This can be useful when one would
like to store some secure field as a digest, just like a password.
The method still defaults to `password`. It now also allows using the
same `#authenticate` method which now accepts a second argument for
specifying the attribute to be authenticated, or will default to 'password`.
A new method is also added for generating a new token for an attribute by
calling `#regenerate_XXXX` where `XXXX` is the attribute name.
|
| | |
|
| |
| |
| |
| |
| | |
This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing
changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa.
|
|/ |
|
| |
|
|
|
|
| |
ActiveModel::SecurePassword
|
| |
|
| |
|
|
ActiveModel::SecurePassword) to encapsulate dead-simple password usage with SHA2 encryption and salting
|