NSX-T Manager Certificate Replacement
I decided it was time to add VMware NSX-T to my HomeLab. I had been putting it off for a while but I couldn’t avoid it any longer!
Once I had fired up my NSX Manager Nodes and Cluster (I am using version 3.1), I looked to installing certificates. I choose to use a single certificate for all 3 of the NSX managers and the cluster using Subject Alternative Names (SAN’s) to simplify the process and this means I don’t need to renew 4 certificates each time.
As this is a different process to other VMware products I have put together a quick run through on how to achieve this.
Firstly, we need to generate the CSR from one of the NSX Manager nodes using openssl. SSH to one of your nodes and run the following command to create a new file called ‘ssl.conf’:
Then populate this file with the below text, changing the values to suit your environment. I have left my values in to help with reading the file. If you are using a single NSX manager in your lab, you can remove the lines for DNS.3, DNS.4, IP.3 and IP.4.
[ req ] default_bits = 2048 distinguished_name = req_distinguished_name req_extensions = req_ext prompt = no [ req_distinguished_name ] countryName = GB stateOrProvinceName = Labshire localityName = Lab City organizationName = SMT-Lab organizationalUnitName = SMT-Lab commonName = vm-nsx-00.smt-lab.local [ req_ext ] subjectAltName = @alt_names [alt_names] DNS.1 = vm-nsx-00.smt-lab.local DNS.2 = vm-nsx-01.smt-lab.local DNS.3 = vm-nsx-02.smt-lab.local DNS.4 = vm-nsx-03.smt-lab.local IP.1 = 10.200.15.34 IP.2 = 10.200.15.35 IP.3 = 10.200.15.36 IP.4 = 10.200.15.37
Now to generate the CSR, run the following, but replacing the files names to suit:
openssl req -out vm-nsx-00.smt-lab.local.csr -newkey rsa:2048 -nodes -keyout vm-nsx-00.smt-lab.local.key -config ssl.conf -sha256
This will generate 2 files in the current working directory. You will have your CSR and the private key. Using something like WinSCP, copy the files off the NSX manager to a location of your choice.
Head off to your CA and issue the certificate using the CSR.
Now you need to copy the root and issuing (if you have an issuing CA) certificate to certificate you just created. This will complete the chain. Also have the private key handy as you are going to need it.
We are now ready to import import the certificate. Head to System > Certificates > Import and select Import Certificate.
Give it a name, browse to the certificate file that now includes the certificate chain, followed by browsing the the private key file. Be sure to change the ‘Service Certificate’ slider to ‘No’ and then click Import.
Once imported you can select it and see that it includes the certificates in the chain.
Now to assign them! Firstly, click on the identifier next to the name and copy the value. This is what will be used to target the certificate in the next steps.
To validate and replace the certificates in NSX we need to use API’s. Using a tool like Postman, validate then replace the certificate on the NSX Manager Cluster by running the following as a GET request. Note you need to provide credentials for the NSX managers on the Authorization tab.
The result of ‘”status” : “ok”‘ is what we are looking for here.
Now its confirmed valid, lets replace the certificate by running the following POST request:
Then its time to apply to all nodes by running each line below:
https://vm-nsx-01.smt-lab.local/api/v1/node/services/http?action=apply_certificate&certificate_id=a94b3600-696b-43bf-a2df-c1e8e2180c3a https://vm-nsx-02.smt-lab.local/api/v1/node/services/http?action=apply_certificate&certificate_id=a94b3600-696b-43bf-a2df-c1e8e2180c3a https://vm-nsx-03.smt-lab.local/api/v1/node/services/http?action=apply_certificate&certificate_id=a94b3600-696b-43bf-a2df-c1e8e2180c3a
And that completes the replacement. If you browse to either your cluster address or individual nodes, you will see your new certificate in place.
You can find the full VMWare documentation on this here.
Thanks for reading!