Upgrading the RSA Authentication Agent for Windows certificates to SHA-256 for offline authentication and agent auto-registration
Originally Published: 2023-01-13
Last Modified: 2024-03-14
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
FIM - Can FIM create SAML assertions signed with SHA256 instead of SHA1? 26Number of Views Agent Auto-Registration 98Number of Views Long URL's cause a the 4.8 Agent for IIS 7 to crash 9Number of Views Upgrading the Internal SecurID Authentication Manager 8.6 Certificates to SHA-256 527Number of Views On-Demand Authentication 13Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?