a3ae35e9c9
Resetting failed attempts after sign in happened inside a warden hook specific for the lockable module, but that was hidden inside the hook implementation and didn't allow any user customization. One such customization needed for example is to direct these updates to a write DB when using a multi-DB setup. With the logic hidden in the warden hook this wasn't possible, now that it's exposed in a model method much like trackable, we can override the model method to wrap it in a connection switch block for example, point to a write DB, and simply call `super`. Closes #5310 Related to #5264 and #5133 |
||
|---|---|---|
| .. | ||
| authenticatable_test.rb | ||
| confirmable_test.rb | ||
| database_authenticatable_test.rb | ||
| lockable_test.rb | ||
| omniauthable_test.rb | ||
| recoverable_test.rb | ||
| registerable_test.rb | ||
| rememberable_test.rb | ||
| serializable_test.rb | ||
| timeoutable_test.rb | ||
| trackable_test.rb | ||
| validatable_test.rb | ||