Using Self-Signed Certificates
The use of self-signed certificates is possible, but not recommended. Not only are self-signed certificates unverifiable, setting up Content Studio to work with self-signed certificates is complicated and error-prone.
A description of how to create and install self-signed certificates for Tomcat is included here: http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html. In order to use Content Studio in combination with self-signed certificates, however, it is also necessary to install certificates on all the computers on which Content Studio is run. For a description of how to do this, see http://blogs.sun.com/andreas/entry/no_more_unable_to_find.
You will also need to set two Java system properties on each machine where Content Studio is run:
javax.net.ssl.trustStore-
The path of the keystore (or trust store) on the computer.
javax.net.ssl.trustStorePassword-
The keystore/certificate password you specified when adding the self-signed certificate. If you did not specify a password, the default is
changeit.
If the certificates are identically installed on all computers
from which Content Studio will be used, then you can include these
settings in the
/com/escenic/webstart/StudioConfig.properties file
in your common configuration layer (see Create the Common Configuration Layer). Otherwise they
will need to be individually set on each computer.