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 … 103Number of Views Determining an existing RSA Prime version 51Number of Views Collect Prime logs and Configuration files using the collect script 160Number of Views RSA Authentication Agent 8.0 for Web for Internet Information Services Generates HTTP Error 500.21 24Number of Views "Authentication station status was 9" error when accessing RSA Authentication Manager Prime Self Service Portal (SSP) with… 351Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?