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 … 114Number of Views Prime kit tomcat.pid: Permission denied error when restarting services for RSA Authentication Manager Prime Kit 106Number of Views QR code not displaying in the RSA Authentication Manager Prime Self-Service Portal (SSP) 356Number of Views Collect Prime logs and Configuration files using the collect script 178Number of Views RSA Authentication Manager Prime services fail to start after Java update on a Windows server: Error Failed creating java 295Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Don't see what you're looking for?