JAR resources in JNLP file are not signed by same certificate

book

Article ID: 39707

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Problem 

After going through the steps given here: 

https://docops.ca.com/ca-release-automation/5-5-2/en/installation/ca-release-automation-communications-security/secure-communications

We are able to successfully access the ROC using https://<servername>:8443. But when we click on Automation Studio to launch ASAP it loads the jnlp, prompts saying that the certificate is not trusted, goes through downloading the jar files and ends/exits with the error: JAR resources in JNLP file are not signed by same certificate

 

Environment

CA Release Automation 5.5.2

 

Cause

The instructions given here: 

https://docops.ca.com/ca-release-automation/5-5-2/en/installation/ca-release-automation-communications-security/secure-communications

mentions the use of a custom-truststore.jar file when it comes to steps 4, 5, and 6. The jar file must be custom-truststore.jar. If it is something other than custom-truststore.jar file then this error will occur. 

 

Resolution

To resolve this issue: 

  1. delete the <other .jar file you created>
  2. create a custom-truststore.jar file as advised in steps 4, 5, and 6
  3. copy the custom-truststore.jar file to the webapps/nolio-app/apps/v2.0.0/lib directory
  4. run the following on your workstation: javaws -uninstall
  5. access the https://<servername>:8443 url again and click on automation studio 

 

The steps above do not require the services to be stopped/started.

 

Additional Information

none

Environment

Release:
Component: RACORE