mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
Corrected login data usage docs
This commit is contained in:
parent
fa9c95fc5d
commit
5445a0d3fc
@ -47,10 +47,13 @@ this unique link will persist across sessions.
|
|||||||
|
|
||||||
## Login Attempts
|
## Login Attempts
|
||||||
|
|
||||||
SilverStripe can be configured to record login attempts, in order to lock out users
|
SilverStripe is configured by default to record login attempts, in order to lock out users
|
||||||
after a defined number of attempts, and hence limit the attack surface of the login process.
|
after a defined number of attempts, and hence limit the attack surface of the login process.
|
||||||
This is predicated on tracking the IP address of the attempt, which can be considered personal data.
|
This is predicated on tracking the IP address of the attempt, which can be considered personal data.
|
||||||
See `SilverStripe\Security\Security::$login_recording` for details.
|
IP addresses related to these attempts are stored indefinitely unless manually purged
|
||||||
|
from the `LoginAttempt` table.
|
||||||
|
See `SilverStripe\Security\Security::$login_recording` and
|
||||||
|
`SilverStripe\Security\Security::$lock_out_after_incorrect_logins` for details.
|
||||||
|
|
||||||
## Logging and Exceptions
|
## Logging and Exceptions
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user