Managing certificates for Informix TLS and SSL encryption

Last Updated : Sep 18, 2024 |
Prolog information
To configure TLS/SSL encryption, you must provide a commercially-signed certificate that is valid for the CMS server and the network where CMS resides. A specific alias must be added to the certificate for Informix stability with TLS/SSL configured. The certificate is verified when you run the ids_tls_configure command.
Note the following requirements for the CA certificate:
  • You are responsible for ensuring your certificate is valid. The certificate must be valid for the CMS server and the network where CMS resides.
  • If you are converting a certificate to the PKCS 12 format, add the alias cms_net_encrypt to your certificate or certificate chain. Specific procedures for adding or converting an alias are not provided due to variations in certificate and certificate chain structures. Industry certificate management utilities, such as Keytool and OpenSSL, enable you to add or convert the alias value.
  • If you have the Java Key Store (JKS) certificate for the CMS Web Client certificate (cmsweb.jks), a PKCS 12 certificate can be exported from the cmsweb.jks certificate as described in Exporting a PKCS 12 certificate from the cmsweb.jks certificate.
Note the full path and the password for the certificate. You will need the path and password to enable Informix TLS/SSL encryption or to update the encryption certificate.
To verify that the alias is in the certificate, run the following command:
keytool -list -v -keystore <Example.p12> -storepass 
<CertificatePassword> | grep Alias