Maintaining the Domain › Manage Certificates › About Using a Certificate Issued by a Third-Party Certificate Authority

About Using a Certificate Issued by a Third-Party Certificate Authority

CA Process Automation supports third-party security certificates for HTTPS web access and signing of jars. Use your own resources to obtain a trusted SSL certificate from the Certificate Authority of your choice. This procedure is beyond to scope of this guide.

The use of third-party security certificates requires the use of third-party tools. The set-up process also requires manual changes to the OasisConfig properties file (install_dir/server/c2o/.config/OasisConfig.properties). Before you begin, become familiar with the basic concepts of security certificates and keystores and the keytool utility provided with the Java JDK.

Implementing third-party security certificates requires updating values for three parameters in the OasisConfig properties file:

• "itpam.web.keystorepath"

  The default value is the keystore path for the self-signed certificate:

  install_dir/server/c2o/.config/c2okeystore
  

• "itpam.web.keystore.password"

  The default value is the encrypted "DOMAINID".

• "itpam.web.keystorealias"

  The default value is ITPAM.

  Note: A keystore can have more than one alias. To use a keystore alias that duplicates an existing alias, remove the existing alias before adding a new instance.

More information:

Oasis Configuration Properties File