Page History

If you are new to certificate management or are looking for a solution that works out-of-the-box then you can use the configuration from the attached archives:

• Download
  • Primary JOC Cockpit configuration: js7-joc-primary.zip
  • Secondary JOC Cockpit configuration: js7-joc-secondary.zip
• The archives include the folders:
  • config.http
    • This folder includes the hibernate.cfg.xml configuration file and default keystore & truststore that are not used with the HTTP protocol.
    • The contents of this folder corresponds to what you get from the default installation of a JOC Cockpit image.
  • config.https
    • This folder includes the hibernate.cfg.xml configuration file and default keystore & truststore..
    • The private key and certificate is created by SOS and works for use with Docker containers that are started for the following hostnames:
      • js7-joc-primary
      • js7-joc-secondary
      • js7-controller-primary
      • js7-controller-secondary
    • As the private key is publicly available you should not consider this a solution to secure your HTTPS connections. However, for evaluation purposes it saves the effort of creating and signing key pairs.
  • To apply the configuration replace the contents of the config folder that is mounted to a JOC Cockpit container with the contents of the config.http or config.https folders respectively.