Discrepancy with user records in RSA IMG prevents users from authenticating
Originally Published: 2015-05-22
Article Number
Applies To
Issue
Workaround
1.Navigate to Resources>Directories.
2. Click on the AD Directory Name that the user should have an account in.
3. Click the Accounts tab.
4. Search for the user_id that cannot login and locate the account that they have.
6. Here, in the box to the right of the new window, you should see the users that are mapped to this account. You should see the other user_id that is terminated here. Click the red 'X' next to the terminated user_id to remove it from the account.
Now, the user should be able to authenticate.
Related Articles
Prevent Users from Authenticating on an Agent 6Number of Views How to configure the RSA Identity Governance and Lifecycle system to prevent users from requesting exceptional access 30Number of Views Unable to Resolve User by Login ID and/or Alias or Authenticator Not Assigned to User When Attempting to Authenticate via … 2.14KNumber of Views IMG: How to setup a request form that allows users to lock/unlock and enable/disable user accounts from IMG 233Number of Views Preventing end users from bypassing the RSA SecurID Access Cloud Authentication Service 51Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings.
Don't see what you're looking for?