By default, Silverstripe gives 10 attempts for user to sign in.
The easiest way to modify the lock out delay and number of attempt in Silverstripe 3 is through config.yml
mysite/_config/config.yml and add the following code:
And voila, your silverstripe lock out system is updated without the need to update the Silverstripe’s core.
If you ever need to access Member’s attribute regarding to lock out, you can use the following: (assuming
$member is an instance of Member class)
Get the date and time of lock validity
Get number of incorrect login attempts that has been done
Check if member is locked
Get the maximum incorrect login attempts from config