You can now replace self-signed or CA-signed appliance certificates from the NSX Manager. You can only replace certificates that have private key and are valid. You cannot replace a certificate that belongs to a service-certificate category.
You can replace the self-signed certificates for the following service types:
- MGMT_CLUSTER (aka VIP)
- CBM_CLUSTER_MANAGER
- K8S_MSG_CLIENT
- CBM_CORFU
- CCP
- APH_TN
- LOCAL_MANAGER
- GLOBAL_MANAGER
- APH (aka APH_AR)
- API
- WEB_PROXY
Note: Note that starting from
NSX 4.2, some certificates have been consolidated. When you replace such a certificate, ensure that the replacing certificate must either have a wild-card SAN entry that matches all the nodes in the cluster and the VIP or it must have as many SAN entries that match the VIP and the individual node addresses.
Going forward, use 'Apply Certificate' when you want to assign individual certificates to services that have been consolidated previously so that they become individual certificates again or to consolidate certificates that have been previously separated. After the de-consolidation of a certificate, use 'Replace Certificate' to renew it or replace it when it has expired.