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 … 113Number of Views Prime kit tomcat.pid: Permission denied error when restarting services for RSA Authentication Manager Prime Kit 104Number of Views Determining an existing RSA Prime version 52Number of Views Collect Prime logs and Configuration files using the collect script 170Number of Views Authentication Manager Node secret mismatch on TMG or UAG 313Number of Views
Trending Articles
How to generate a PASSCODE for manual entry on a Ericsson R380 WAP phone RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?