This topic gives you an overview of how to prepare for using Transport Layer Security (TLS) with VMware Tanzu RabbitMQ for Tanzu Application Service to secure communication between apps and service instances.
CautionThis procedure involves restarting all of the VMs in your deployment to apply a CA certificate. The operation can take a long time to complete.
When you use TLS, you are provisioned a Tanzu RabbitMQ for Tanzu Application Service server with a certificate. With this certificate, apps and clients can establish an encrypted connection with the service.
Using BOSH CredHub, Tanzu Operations Manager generates a server certificate using a Certificate Authority (CA) certificate.
If you do not want to use the CA certificate generated, you can provide your own CA certificate and add it through the CredHub CLI. For an overview of the purpose and capabilities of the CredHub component, see CredHub.
Apps and clients use this CA certificate to verify that the server certificate is trustworthy. A trustworthy server certificate allows apps and clients to securely communicate with the Tanzu RabbitMQ for Tanzu Application Service server.
VMware Tanzu Application Service for VMs (TAS for VMs) shares the CA certificate public component:
Tanzu Operations Manager can generate a CA certificate for TLS to use.
Alternatively, you can choose to provide your own CA certificate for TLS to use.
The workflow you follow to prepare for TLS depends on whether you use the CA certificate generated by Tanzu Operations Manager or if you bring your own CA certificate.
To use the CA certificate that Tanzu Operations Manager generates through CredHub, follow this workflow to enable TLS for VMware Tanzu RabbitMQ for Tanzu Application Service:
An operator adds the CredHub-generated certificate to Tanzu Operations Manager by performing the procedures:
An operator enables TLS in the tile configuration while installing Tanzu RabbitMQ for Tanzu Application Service. See Enable TLS in Tanzu RabbitMQ for Tanzu Application Service.
To provide your own CA certificate instead of using the one that Tanzu Operations Manager generates, follow this workflow to enable TLS for VMware Tanzu RabbitMQ for Tanzu Application Service:
An operator provides a CA certificate to CredHub by performing the procedures:
An operator enables TLS in the tile configuration while installing Tanzu RabbitMQ for Tanzu Application Service. See Enable TLS in Tanzu RabbitMQ for Tanzu Application Service.
To find the BOSH CredHub client name and client secret:
Record the values for BOSH_CLIENT
and BOSH_CLIENT_SECRET
.
Here is an example of the credentials page:
{"credential":"BOSH_CLIENT=ops_manager
BOSH_CLIENT_SECRET=abCdE1FgHIjkL2m3n-3PqrsT4EUVwXy5
BOSH_CA_CERT=/var/tempest/workspaces/default/root_ca_certificate
BOSH_ENVIRONMENT=10.0.0.5 bosh "}
The BOSH_CLIENT
is the BOSH CredHub client name and the BOSH_CLIENT_SECRET
is the BOSH CredHub client secret.
Prerequisite: To complete this procedure, you must have the CredHub CLI. For installation instructions, see credhub-cli on GitHub.
Do this procedure if you are providing your own custom CA certificate instead of using the one generated by Tanzu Operations Manager or CredHub.
To add a custom CA Certificate to CredHub:
Record the information needed to log in to the BOSH Director VM by following the procedure in Gather Credential and IP Address Information.
Log in to the Ops Manager VM by following the procedure in Log in to the Ops Manager VM with SSH.
Set the API target of the CredHub CLI as your CredHub server by running:
credhub api \
https://BOSH-DIRECTOR-IP:8844 \
--ca-cert=/var/tempest/workspaces/default/root_ca_certificate
Where BOSH-DIRECTOR-IP
is the IP address of the BOSH Director VM.
For example:
$ credhub api \
https://10.0.0.5:8844 \
--ca-cert=/var/tempest/workspaces/default/root\_ca\_certificate
Log in to CredHub by running:
credhub login \
--client-name=CREDHUB-CLIENT-NAME \
--client-secret=CREDHUB-CLIENT-SECRET
Where:
CREDHUB-CLIENT-NAME
is the value you recorded for BOSH_CLIENT
in Find the CredHub Credentials in Ops Manager.CREDHUB-CLIENT-SECRET
is the value you recorded for BOSH_CLIENT_SECRET
in Find the CredHub Credentials in Ops Manager.For example:
$ credhub login \
--client-name=credhub \
--client-secret=abcdefghijklm123456789
Use the CredHub CLI to provide a CA certificate. Your deployment can have multiple CA certificates. VMware recommends a dedicated CA certificate for services. Create a new file called root.pem
with the contents of the certificate. Then, run the following command, specifying the path to root.pem
and the private key for the certificate. For example:
$ credhub set \
--name="/services/tls_ca" \
--type="certificate" \
--certificate=./root.pem \
--private=ERKSOSMFF...
Prerequisite: To complete this procedure, you must have the CredHub CLI. For installation instructions, see credhub-cli on GitHub.
To add the CA Certificate to Ops Manager:
Record the CA certificate by running:
credhub get \
--name=/services/tls_ca \
-k ca
Go to Ops Manager Installation Dashboard > BOSH Director > Security.
Append the contents of the CA certificate you recorded in an earlier step into Trusted Certificates.
Click Save.
To enable TLS in the Tanzu RabbitMQ for Tanzu Application Service tile: