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
Contact Lists for Authentication Requests Number of Views RSA SecurID Access Authenticate App message "PIN cannot be reset, Contact your administrator." Number of Views RSA Identity Governance & Lifecycle Export of Review Results in PDF or CSV format does not include the correct values in t… Number of Views RSA Web Threat Detection - Delayed Transactions Not in Shard File for the Correct Hour Number of Views Running a form incorrectly filters on raw name when filtering on the Application Name attribute in RSA Identity Governance… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.5 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. Self-Service Console Returns Error 404 Not Found When Accessed via Web-Tier in RSA Authentication Manager 8.x
Don't see what you're looking for?
