Skip to content

Conversation

cesartalves
Copy link

@cesartalves cesartalves commented Oct 11, 2022

Locking Admin users after consecutive failed attempts is a good practice to prevent Brute Force password detection.

This adds the necessary backbone (controller, routes and email template) so that using the lockable strategy with the extension requires minimal work over it.

I added the unlockable controllers only on the Admin side as I believe it's the most useful / pressing.
Thankfully the migrations and translations were already included which made this change pretty slim!

Locking Admin users after consecutive failed attempts is a good practice to prevent Brute Force password detection.

This adds the necessary backbone (controller, routes and email template) so that using the lockable strategy with the extension requires minimal work over it.
@cesartalves cesartalves force-pushed the cesartalvez/add-lockable-option branch 4 times, most recently from 92b7e88 to 483a40c Compare October 18, 2022 14:17
@cesartalves cesartalves force-pushed the cesartalvez/add-lockable-option branch from 483a40c to 33da025 Compare October 18, 2022 14:44
@cesartalves cesartalves marked this pull request as ready for review October 24, 2022 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant