RSA Authentication Agent for Microsoft Windows Is Not Authenticating Against the Correct Contact List
Originally Published: 2023-02-06
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
Issue
Cause
Deleting this file will refresh the list available Authentication Manager instances.
Note: The sdstatus.12 is automatically created by default on the next authentication.
Resolution
- Login to the Windows machine where the RSA Authentication Agent for Microsoft Windows is installed.
- Navigate to the path where the agent's configuration files are stored. The default path is C:\Program Files\Common Files\RSA Shared\Auth Data
- Delete the sdstatus.12 file.
- Open the RSA Control Center and test the authentication. The requests will now be hitting the correct Contact List.
Related Articles
RSA SecurID Access Authenticate App message "PIN cannot be reset, Contact your administrator." 148Number of Views Contact Lists for Authentication Requests 86Number of Views Running a form incorrectly filters on raw name when filtering on the Application Name attribute in RSA Identity Governance… 37Number of Views RSA Web Threat Detection - Delayed Transactions Not in Shard File for the Correct Hour 10Number of Views Authentication Manager agent / server contact list and the sdconf.rec file 372Number of Views
Trending Articles
Troubleshooting RSA MFA Agent for Microsoft Windows RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Deploy an Identity Router Virtual Machine in Microsoft Azure
Don't see what you're looking for?