Managing certificates

Set up custom TLS certificates for connecting to the platform and CA certificates to connect to internal servers from the platform.

Creating a secret to store shared custom certificates
You can create a secret called cpd-custom-ca-certs that contains a set of custom certificates. You can run the gen-platform-ca-certs to inject the secret, the secret mount, and associated environment variables into IBM Software Hub pods so that they have access to the custom certificates.
Using a custom TLS certificate for HTTPS connections to the platform
IBM Software Hub includes a self-signed TLS certificate that is used to enable HTTPS connections. However, this certificate is untrusted by all HTTPS clients. It is strongly recommended that you replace the self-signed certificate with your own certificate.
Using a CA certificate to connect to internal servers from the platform
If you want to enable the IBM Software Hub platform to use your company's CA certificate to validate certificates from your internal servers, you must create a secret that contains the CA certificate. Additionally, if your internal servers use an SSL certificate that is signed using your company's CA certificate, you must create this secret to enable the platform to connect to the servers.
Enabling IBM Software Hub administrators to manage certificate renewal dates
You can configure IBM Software Hub so that IBM Software Hub administrators can control when internal certificates are renewed.

Parent topic: Securing your IBM Software Hub environment