Run as Different User option generated a node secret mismatch with RSA Authentication Agent 7.2.1
Originally Published: 2012-12-11
Last Modified: 2023-10-06
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
RSA MFA Agent 9.0 for Microsoft IIS Third Party Licenses 21Number of Views Node secret mismatch: agent and server using different node secrets when authenticating from Citrix Web Interface 5.4 with… 740Number of Views Run as a different user prompts for a passcode not password with RSA Authentication Agent 7.4 for Windows 257Number of Views RSA MFA Agent 9.0 for Apache Third Party Licenses 13Number of Views This token type is not allowed error in RSA Authentication Manager 8.x Self-Service Console 112Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?