How to update/change certificate for Configuration Manager UI on a TIBCO Cloud API Management - Local Edition cluster?
book
Article ID: KB0072643
calendar_today
Updated On:
Products
TIBCO Cloud API Management - Local Edition
Description
The steps below are for a CAPIM-LE Cluster on Docker+Swarm and should be modified as per the environment. The documentation chapter "Preparing KeyStores for Configuration Manager" also has the below steps to be performed on via tml-installer's Jenkins UI.
Issue/Introduction
This article provides inputs on updating/changing certificate/keystore for the Configuration Manager UI(CM-UI) on an existing CAPIM-LE cluster.
Environment
All Supported Platforms
Resolution
> There are four files that need to be updated: - tml-cm.jks - tml-cm-crt.pem - tml-cm-key.pk8 - tml_cm_properties.json
> Get the new certificate and key in the below formats: - tml-cm.jks - tml-cm-crt.pem - tml-cm-key.pk8 (this way yml and env files need not be updated) -> Please make sure the store password for the jks as well as .pk8 are same. -> Also the store password and entry password for tml-cm.jks should be the same.
> Update the keystore password in tml_cm_properties.jks "cm_keystore_password": "password"
> Place the above updated files inside the manifest flder
> Undeploy the cm pod: ./undeploy-cm-pod.sh
> Deploy the cm pod: ./deploy-cm-pod.sh
Note: - the default keystore password is changeme - the password for my sample is: password - Please see attached vijay_samples.zip for reference
Attachments
How to update/change certificate for Configuration Manager UI on a TIBCO Cloud API Management - Local Edition cluster?
get_app