VMware NSX
A PI certificate is used for authentication with a remote entity, NSX will have the certificate (not the key), the remote entity will own the certificate and the key.
When the remote entity makes an authentication request using the PI user, NSX presents the certificate and the remote entity will use the key it has to verify the connection.
NSX Self Signed Certificate
Self Signed Certificates generated on NSX can not be used for PI connections to NSX.
CA Signed Certificate
The remote entity should generate a CA signed certificate with key and retain the key and certificate.
Use the certificate when creating the PI user in NSX.
Since NSX 4.2.1, the certificate can be replaced in the NSX UI, prior to this, it was only possible using API calls.
If you are on a version prior to 4.2.1 or API use is preferred, use the following procedure.
GET https://<nsx-mgr>/api/v1/trust-management/principal-identitiesPOST https://<nsx-mgr>/api/v1/trust-management/principal-identities?action=update_certificate{ "principal_identity_id": "########-####-####-####-############", "certificate_id" : "########-####-####-####-############"}Note: Do not use this procedure to replace Local Manager or Global Manager principal identity certificates Replace Certificates Through API
More details on Importing/Replacing PI Certificates can be found in the Administration Guide Add a Role Assignment or Principal Identity