Tasktop Error "CCRTT-30014E: Server Certificate Could Not Be Verified" After Test Manager SSL Certificate Change

After changing the SSL certificate on the Test Manager server, the connection from Tasktop Hub to the Test Manager repository fails. Is there any additional configuration required on the Tasktop side to ensure the connection remains secure and trusted?

Issue Description

After updating the SSL certificate on the Test Manager server, users are unable to connect Tasktop Hub to the Test Manager repository. When attempting to establish the connection, the following error message appears:

"Error communicating with repository. Insecure connections are not allowed.

Insecure Repository Connection: Server certificate could not be verified (CCRTT-30014E)"

Root Cause

Although the new certificate has been correctly installed and added to the Trusted Root Certification Authorities on the Test Manager server, Tasktop still fails to verify the certificate chain. This happens because Tasktop uses its own Java Runtime Environment (JRE) truststore, which does not automatically include new or updated SSL certificates from the operating system.

As a result, Tasktop treats the connection as insecure and prevents communication with the Test Manager repository until the updated SSL certificate (and any intermediate/root certificates) are manually imported into the JRE truststore.

Resolution

Follow these steps to import the new SSL certificate chain into the Tasktop JRE truststore:

  1. Shut down your Tasktop Hub instance.
  2. Export the SSL certificates from the Test Manager server:
    • Open your browser and navigate to the Test Manager URL (e.g., https://<TestManagerServer>/).
    • Click on the padlock icon in the address bar.
    • Select View Certificates → Details tab → Copy to File...
    • Choose DER encoded binary X.509 (.CER) format.
    • Export each certificate in the chain (server, intermediate, and root certificates).
  3. Save the certificates to a local folder, for example: C:\SSL\
    • Import the certificates into the Tasktop JRE truststore:
      • Run the following command in Command Prompt for each exported certificate:
        • <path_to_jre>\bin\keytool -import -trustcacerts -keystore <path_to_jre>\lib\security\cacerts -file C:\SSL\my_ca.cer -alias myca
      • Replace:<path_to_jre> → Path to the JRE folder in your Tasktop Hub installation.
        • my_ca.cer → Name of your exported certificate file.
        • myca → Unique alias name for each certificate.
      • When prompted for a password, use the default: changeit
  4. Restart the Tasktop Hub service.
  5. Reconnect to the Test Manager repository and verify that the connection succeeds.