How to reset the RSA Authentication Manager 8.x system fingerprint
Originally Published: 2015-07-31
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.x
Resolution
Use the CLI to reset the system fingerprint of the server
- SSH to the primary Authentication Manager server.
-
Login to the CLI:
login as: rsaadmin Keyboard-interactive authentication prompts from server: Password: <enter operating system password> RSA Authentication Manager Installation Directory: /opt/rsa/am
- Navigate to rsa/opt/rsa/am/utils:
cd /opt/rsa/am/utils
-
Run the following command:
./rsautil manage-secrets -a recover
- When prompted, enter your Operations Console user ID and password
Please enter OC Administrator username: <enter Operations Console admin user name> Please enter OC Administrator password:<enter Operations Console admin password> Machine fingerprint restored successfully.
- Once the fingerprint is reset start or restart all the RSA services on the Authentication Manager.
Related Articles
How to recover when RSA Authentication Manager 8.x system passwords are not known or are lost 2.98KNumber of Views How to factory reset an RSA SecurID hardware appliance running Authentication Manager 8.2 without using the installation I… 629Number of Views How to recover the user id or password of a read only database user from RSA Authentication Manager 8.x 271Number of Views How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… 1.93KNumber of Views RSA Via Lifecycle and Governance access control setting for web services gets reset to default on server restart 95Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?