Orchestrator provides an SSL certificate that controls user access to Web views. You can configure Orchestrator to use a different SSL certificate to control access to Web views, for example if your company security policy requires you to use their SSL certificates.
Prerequisites
Make sure that you have generated or installed an SSL certificate signed by a CA.
Procedure
1 | Open the server.xml configuration file in a text editor.
The default location is:
/opt/vmo/app-server/server/vmo/deploy/jboss-deploy-tomcat/jbossweb-tomcat55.sar/server.xml
|
2 | Find the following entry in the server.xml file.
<!-- Define a SSL HTTP/1.1 Connector on port ${ch.dunes.https-server.port} -->
<Connector address="${jboss.bind.address}" protocol="HTTP/1.1" SSLEnabled="true" clientAuth="false" emptySessionPath="true"
keystoreFile="${java.home}/lib/security/jssecacerts"
keystorePass="dunesdunes"
|
3 | Change the keystoreFile and keystorePass attributes to refer to the <your_keystore_filename> file and the password you created when you ran the keytool utility.
keystoreFile="/PathToKeystore/<your_keystore_filename>"
keystorePass="NewKeystorePassword"
The keystoreFile attribute should contain slashes as directory separators.
|
4 | Save the server.xml file and restart the Orchestrator server. |
You changed the SSL certificate that the Orchestrator server uses to control access to Web views.