RSA Authentication Agent for Microsoft Windows Is Not Authenticating Against the Correct Contact List
Originally Published: 2023-02-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 Identity Governance & Lifecycle Export of Review Results in PDF or CSV format does not include the correct values in t… Number of Views Using the correct version of WebLogic Number of Views RSA ACE/Agent for Web gives access to protected pages when correct passcode is used Number of Views Determine the correct root (base DN) and user search filter when configuring an identity source for the RSA SecurID Access… Number of Views RSA Web Threat Detection - Delayed Transactions Not in Shard File for the Correct Hour Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
