About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Using custom certificates
Last updated: Apr 03, 2024
Learn how to use a custom certificate for License Service API over https.
Configuring a custom certificate for License Service
To configure a custom certificate for License Service communication, complete the following steps:
-
Change the certificate name to
.tls.crt
-
Change the name of the key to
.tls.key
-
Run the following command to change the directory to where the certificate and the key are stored:
cd <certificate_directory>
-
Create a secret by using the following command:
licensingNamespace=$(oc get pods --all-namespaces | grep "ibm-licensing-service-" | awk {'print $1'}) kubectl create secret tls ibm-licensing-certs --key tls.key --cert tls.crt -n ${licensingNamespace}
-
Edit the IBMLicensing custom resource to include the certificate. Add the following parameters to the
section, underIBMLicensing
:spec
-
To enable the
connection, add the following line:https
httpsEnable: true
-
To apply the custom certificate that you created in step 4 as
, add the following line:ibm-licensing-certs
httpsCertsSource: custom
For example:
apiVersion: operator.ibm.com/v1alpha1 kind: IBMLicensing metadata: name: instance spec: httpsEnable: true httpsCertsSource: custom
-
When you change or replace a Custom Certificate to get the new Certificate, applied to the License Service, make sure to delete the
pod. This operation forces restart of the License Service with updated
certificate.ibm-licensing-operator-xxxx
Was the topic helpful?
0/1000