The following table provides lockout information for RSA SecurID Access authentication methods.
|Authentication Method||Lockout Information|
You can configure the number of times users can retry each tokencode method after the first unsuccessful authentication. After this many retries, the tokencode is locked. Each method is locked separately. For example, if you allow three retries, the Authenticate Tokencode is locked after four unsuccessful attempts and the SMS Tokencode is locked after four unsuccessful attempts. Resending the SMS Tokencode counts as a retry, even if the user did not attempt authentication. During lockout, the method cannot be used. The user's Cloud Authentication Service account is not locked or disabled.
A Super Admin or Help Desk Administrator must unlock the method on the Users > Management page. Both tokencode methods are unlocked simultaneously. The lockout counter is cleared after the user successfully authenticates. To configure lockout, see Configure Session and Authentication Method Settings.
|LDAP Directory Password||You can configure the number of unsuccessful attempts before the Cloud Authentication Service locks this method. During lockout, the Cloud Authentication Service ignores a user's password attempts until the lockout duration expires. To configure lockout, see Configure Session and Authentication Method Settings.|
|RSA SecurID Token||RSA Authentication Manager controls lockout for this method.|
|Fingerprint Verification||The iOS and Android operating systems can lock fingerprint verification on the user's mobile device.|
|FIDO Token||Cannot be locked. You can delete a user's FIDO Token from RSA SecurID Access, forcing the user to re-register the token the next time it is used.|
|Eyeprint ID||Cannot be locked. After three unsuccessful authentication attempts, the user must restart the authentication process.|
|Approve||Cannot be locked. After 60 seconds, the user must restart the authentication process.|