Upgrading the RSA Authentication Agent for Windows certificates to SHA-256 for offline authentication and agent auto-registration
Originally Published: 2023-01-13
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Microsoft Windows, Authentication Manager
RSA Version/Condition: 7.4.x, 8.6 or above
Issue
Resolution
Prerequisites
- If you do not have copies of your Authentication Manager license files, request them by opening a case with the Customer Asset Management (CAM) team. Select CAM when presented with the rsaadmin@primarycase types.
- Take a backup of the Authentication Manager database though the Operations Console (Maintenance > Backup > Backup Now). It is also recommended to take snapshot, if this is a virtual server prior to the change.
- Unzip the contents of the license.zip.
- Using WinSCP or a similar SCP client, copy the files to /home/admin to the Authentication Manager primary server.
- Using PuTTY or a similar SSH client, connect to the Authentication Manager primary using the rsaadmin user name and operating system password..
- Navigate to /opt/rsa/am/utils and run the following command:
rsaadmin@primary:/opt.rsa.am> cd /opt/rsa/am/utils
rsaadmin@primary:/opt/rsa/am/utils> ./rsautil install-am-keystore -a <Ops Console administrator name> -w <Ops Console administrator password> -l ~/. -r
Server certificate, key and SDTI certificate are installed successfully.
rsaadmin@primary:/opt/rsa/am/utils> ./rsautil install-am-keystore -a <Ops Console administrator name> -w <Ops Console administrator password> -l ~/. -r
Server certificate, key and SDTI certificate are installed successfully.
For example:
./rsautil install-am-keystore -a ocadmin -w support1! -l ~/. -r
Server certiicate, key and SDTI certificate are installed successfully.
- Restart all Authentication Manager services:
/opt/rsa/am/server/rsaserv restart all
- Once all services are running, the certificates are upgraded after the services restart.
- Log into the Security Console.
- Download the agent's new server.cer file from the Security Console (Access > Authentication Agents > Download Server Certificate File > Download Now).
- Verify that the new certificate is using SHA-256.
- Repeat steps 2 through 9 for all replicas.
Notes
- Subsequent auto-registration attempts might fail due to the SHA-1 server.cer presence. To resolve this,
- Download the new server.cer file and copy it to C:\Program Files\RSA\RSA Authentication Agent\Agenthost Autoreg Utility.
- Restart RSA Authentication Agent Auto-Registration from Windows Services on the Windows machine hosting the RSA Authentication Agent.
Related Articles
Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256 490Number of Views Configure Device Registration for a Risk-Based Authentication Policy 7Number of Views Agent Auto-Registration 93Number of Views How to manually update the internal SHA-1 certificates used by earlier versions of Authentication Manager after upgrading … 980Number of Views Cerby - SCIM Configuration - RSA Ready Implementation Guide 21Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?