The login procedure is protected in addition by a mechanism which prevents a hacker to try and force-guess passwords by slowing down attempts to log in into the same account. Every login attempt is recorded, and stored for a while (currently ten minutes), and each login attempt during that time incurs a penalty of 2^login attempts milliseconds - that is, 10 login attempts incur a login penalty of 1.024 seconds. The delay is currently capped to 20 seconds. @author Andrew Jaquith @author Erik Bunn @since 2.3
If the authentication is successful, the manager is responsible for producing an {@link AuthenticationResult} containing the user's main {@link Principal} and zero ormore other implementation-specific principals.
The {@link #initialise()} method is responsible for registering SASL mechanisms required bythe manager. The {@link #close()} method must reverse this registration.
The login procedure is protected in addition by a mechanism which prevents a hacker to try and force-guess passwords by slowing down attempts to log in into the same account. Every login attempt is recorded, and stored for a while (currently ten minutes), and each login attempt during that time incurs a penalty of 2^login attempts milliseconds - that is, 10 login attempts incur a login penalty of 1.024 seconds. The delay is currently capped to 20 seconds. @since 2.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|