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 the display of user information thumbnail when the screen is locked in RSA Authentication Agent 7.x for Windows 40Number of Views Disable a User Account 18Number of Views IMG: How to setup a request form that allows users to lock/unlock and enable/disable user accounts from IMG 226Number of Views RSA Governance & Lifecycle Recipes: Overview - User Accounts 27Number of Views 'ORA-28000: the account is locked' error when migrating an imported database in RSA Identity Governance & Lifecycle 186Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…