Introduction
In 2024, Google announced its plan to discontinue support for Entrust Certificate Authority (CA) in Google Services (such as Chrome, one of the most used Web Browsers) by October 2025 (Reference: Google Online Security Blog: Sustaining Digital Certificate Security - Entrust Certificate Distrust).
Prior to this announcement, RSA used Entrust CA in RSA Cloud Access Service (formerly known as RSA Cloud Authentication Service), and in applications such as RSA Authentication Manager, RSA Authenticate app, RSA Authenticator app, and RSA Prime.
As a result, RSA is therefore moving to a new CA in the week commencing October 06, 2025, which is already included in the latest versions of RSA Authentication Manager and RSA Authenticator app.
Affected Products
- All PrimeKit versions supporting hybrid use cases connected to RSA Cloud Access Service.
- Other RSA products affected by the same issue are covered under different advisories.
Required Actions
- To maintain trust and service continuity in RSA Prime, DigiCert root and intermediate certificates must be added to the Java truststore used by Prime before Monday, October 06, 2025.
- Two methods are available for installing the certificates; choose only one approach:
- An automated approach using the provided scripts (recommended).
- A manual step-by-step procedure for environments where scripting is not feasible.
What does the Script do?
- Validates if DigiCertCA2025 and DigiCertRA2025 already exist in the truststore.
- Prompts for the truststore password.
- Generates and writes the embedded DigiCert Root and Intermediate certificate files.
- Imports both certificates into truststore.jks
- Outputs success or failure for each certificate import.
First Option (recommended) - Script Instructions
- Download the attached script based on the host OS type:
a. Linux: update_digicert_truststore.sh
b. Windows: update_digicert_truststore.ps1
c. Upload the downloaded script to <Prime_Home>/scripts/tools - For Linux systems:
- Navigate to <Prime_Home>/scripts/tools directory
cd /<Prime_Home>/scripts/tools - Reset the Permissions
./3_reset_perms.sh - Execute the script
./linux_update_digicert_truststore.sh - Restart AMIS service:
cd .. ./amis_shutdown.sh ./amis_startup.sh
- Navigate to <Prime_Home>/scripts/tools directory
- For Windows systems:
- Run PowerShell as an administrator
- Navigate to [Prime_Home}\scripts\tools
[Prime_Home}\scripts\tools - Execute the script
./windows_update_digicert_truststore.ps1 - Restart RSA AMIS (Tomcat) from the Windows Services
Second Option - Manual Instructions
- Obtain DigiCert's root and intermediate CA certificates
- Upload the ceritificates to <Prime_Home>/certificates
- Note: Make sure that the certificate name is as follows:
- Root Certificate: DigiCertRootCA.crt
- Intermediate Certificate: DigiCertIntermediateCA.crt
- Note: Make sure that the certificate name is as follows:
- Import the certificates using keytool:
- Change to <Prime_Home>/certificate
- Execute the following command to import the DigiCert root certificate
For Linux:
../java/latest/bin/keytool -importcert -alias digicertroot -keystore truststore.jks -file DigiCertRootCA.crtFor Windows:
..\java\latest\bin\keytool.exe -importcert -alias digicertroot -keystore truststore.jks -file DigiCertRootCA.crt - Execute the following command to import the DigiCert intermediate certificate
For Linux:
../java/latest/bin/keytool -importcert -alias digicertintermediate -keystore truststore.jks -file DigiCertIntermediateCA.crtFor Windows:
..\java\latest\bin\keytool.exe -importcert -alias digicertintermediate -keystore truststore.jks -file DigiCertIntermediateCA.crt - You will be prompted to provide the truststore password
- Restart the AMIS service.
- For Linux systems:
cd .. ./amis_shutdown.sh ./amis_startup.sh - Restart RSA AMIS (Tomcat) from the Windows Services
- For Linux systems:
If you need any help, contact the RSA Support Team.
Related Articles
Prime kit tomcat.pid: Permission denied error when restarting services for RSA Authentication Manager Prime Kit 91Number of Views Collect Prime logs and Configuration files using the collect script 136Number of Views Determining an existing RSA Prime version 51Number of Views "Authentication station status was 9" error when accessing RSA Authentication Manager Prime Self Service Portal (SSP) with… 348Number of Views How to enable HTTP Strict Transport Security (HSTS) Header on Authentication Manager Prime Self-Service Portal 33Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process