Run as Different User option generated a node secret mismatch with RSA Authentication Agent 7.2.1
Originally Published: 2012-12-11
Article Number
Applies To
RSA Product/Service Type: RSA Authentication Agent
RSA Version/Condition: 7.2.1
Platform: Windows
Issue
The RSA Authentication Manager real-time authentication activity monitor reports the following error after using the Run as different user option on Microsoft Windows 2012 R2 where RSA Authentication Agent 7.2.1 for Windows is installed and configured:
Node secret mismatch: cleared on agent but not on server
Cause
Resolution
The Windows administrator could deactivate User Access Control (UAC) to resolve access issues to the node secret file and Microsoft has provided information on this. Please visit Windows Server 2012: Deactivating UAC for more information on deactivating the UAC.
Where UAC is required, the administrator would change the permissions on the node secret file to use read access for authenticated users.
Notes
Related Articles
Node secret mismatch: agent and server using different node secrets when authenticating from Citrix Web Interface 5.4 with… 719Number of Views How to recreate the node secret for RADIUS Server in RSA Authentication Manager 8.x 944Number of Views Authentication Manager Node secret mismatch on TMG or UAG 308Number of Views Delete a User 14Number of Views RSA Authentication Manager Prime throws "Node secret mismatch: cleared on server but not on agent" despite repeated cleari… 501Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?