Locked User Accounts
When a user account is locked, the user cannot authenticate and access protected resources. A user account can be locked in two ways:
Lockout policy. This policy locks a user account if authentication fails a specified number of times using the primary authentication method. Lockout policies apply to the total number of logon attempts a user makes regardless of the type of credential used for each attempt.
Note: If the lockout policy is configured to unlock a user after a certain period of time, the user will be unlocked when the time expires. The user will show as “True” (locked) in the Locked Out field in reports until the next successful authentication.
Token policies. Token policies determine RSA SecurID PIN lifetime and format, and fixed passcode lifetime and format. They are assigned to security domains and apply to all tokens assigned to users managed by a given security domain. If a user puts the wrong tokencode in a specified number of times, they will be locked out.
Related Articles
Disable a User Account 12Number of Views Mapping Accounts to Deleted Users in RSA Identity Lifecycle and Goverance 126Number of Views Enable a User Account 2Number of Views IMG: How to setup a request form that allows users to lock/unlock and enable/disable user accounts from IMG 221Number of Views Disable the display of user information thumbnail when the screen is locked in RSA Authentication Agent 7.x for Windows 40Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.4 for Microsoft Windows Installation and Administration Guide Downloading RSA Authentication Manager license files or RSA Software token seed records Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Release Notes for RSA Authentication Manager 8.8