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 21Number of Views Disable an RSA Authentication Manager user account using the Administration API 50Number of Views IMG: How to setup a request form that allows users to lock/unlock and enable/disable user accounts from IMG 236Number of Views In RSA Via Lifecycle and Governance the Allow Multiple Selections checkbox is disabled for the User Accounts Table in the … 54Number of Views Managing User Accounts 22Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme