Skip to content

← All integrations

Storage and virtualisation

Renews vCenter’s Machine SSL certificate and checks API and served TLS identity.

The appliance runs the integration and connects to VMware vCenter through vSphere REST / VI JSON API over HTTPS on port 443. No service agent is installed on VMware vCenter.

What happens

  1. The appliance connects to VMware vCenter through vSphere REST / VI JSON API on port 443.
  2. The integration checks RSA certificate, key and chain and replaces vCenter’s Machine SSL identity with one REST call. Managed ESXi certificates are unchanged.
  3. Any service restart is awaited. A fresh TLS handshake and a new API session must both show the new certificate.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to vSphere REST / VI JSON API, port 443. No service agent is installed.
Service ports
443
What you need
Replacing the Machine SSL certificate needs administrator@vsphere.local or an account in the single sign-on group CAAdmins. To use another account: vSphere Client > Administration > Single Sign On > Users and Groups > Groups > CAAdmins > Add members. Enter the account as user@domain (for example administrator@vsphere.local) and its password here.
Platform
vCenter 7.0 U2+, vSphere Automation REST API /api
Actions
Discovery, Installation, Verification, Rollback
Integrations
vmware-vcenter-api 2.0.0
Note
  • Automatic restoration and rollback require previous matching certificate and key as inputs. vCenter returns no private key. A silent vCenter can still be starting and is not blindly overwritten; run verify. Later certificate changes are preserved. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts.

Next steps