RSA Authentication Manager Prime throws "Node secret mismatch: cleared on server but not on agent" despite repeated clearing of the secret
Originally Published: 2018-08-21
Article Number
Applies To
RSA Product/Service Type: Authentication Manager Prime/Authentication Manager Integration Service (AMIS)
Issue
Node secret mismatch: cleared on server but not on agent
Cause
Clearing the node secret on the AMIS machine under ..\RSA\amis\auth makes no difference, as AMIS still continues to look for the node secret file in C:\RSA\amis\auth\securid and simply rejects the authentication request, as it cannot find one there.
Resolution
- Delete the securid file under ..\RSA\amis\auth on the AMIS machine.
- Update the rsa_api.properties file so that the SDNDSCRT_LOC points to C:\RSA\amis\auth.
Related Articles
Mandatory Update: DigiCert Certificate Configuration for RSA Prime (Required by October 06, 2025 for Cloud Access Service … 99Number of Views Authentication Manager Node secret mismatch on TMG or UAG 309Number of Views Node secret mismatch: agent and server using different node secrets when authenticating from Citrix Web Interface 5.4 with… 724Number of Views Determining an existing RSA Prime version 51Number of Views Collect Prime logs and Configuration files using the collect script 148Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Unable to login to RSA Authentication Manager Security Console as super admin Error Unable to resolve user by login ID and/or alias, or authenticator not assigned to user when attempting to authentica…
Don't see what you're looking for?