The certificate used is a symlink to a host-specific certificate. Each TrilioVault VM has its own self-signed certificate by default which is getting recreated every time the TVault-Config service is restarted.
When the certificate for the TVault-Config and Nginx (Grafana) is to be changed to a customer chosen certificate it is required to deactivate the recreation of the certificates upon service restart.
Trilio is planning to change this behavior to make it easier for customers to change the certificate in the future.
1.
Login into the TrilioVault VM via SSH
2.
Edit the following file:
/home/stack/myansible/lib/python3.6/site-packages/tvault_configurator/tvault_config_bottle.py
3.
Look for create_ssl_certificates() in the main function
4.
Comment out create_ssl_certificates()
5.
Repeat for all nodes of the TrilioVault cluster
The resulting main function will look like this:
1
def main():
2
# configure the networking
3
#create_ssl_certificates()
4
​
5
http_thread = Thread(target=main_http)
6
http_thread.daemon = True # thread dies with the program
Changing the certificate used by Nginx for wlm-api service
The certificate provided by the Nginx for the wlm-api service is set during configuration when HTTPS endpoints are configured for the TrilioVault appliance.
This certificate is provided to the end-user or Openstack every time an API call to the TrilioVault solution is sent.
To change the certificate through the configurator make sure to create HTTPS endpoints and upload the certificate and key using the advanced options of the configurator.
Setting HTTPS at the advanced options
The certificates can be changed manually if necessary.