Academy/VCAP — VCF Administrator (3V0-11.26)/Lab: Certificate Lifecycle — CA-Signed Replacement & Auto-Renewal in VCF Operations
This lab targets VCF 9.0

Lab: Certificate Lifecycle — CA-Signed Replacement & Auto-Renewal in VCF Operations

VCF 9.0Advancedvcap-advanced⏱ 120 min

Certificate management in VCF Operations: CA configuration, CA-signed replacement, auto-renewal, certificate alerts

Objectives

  • Configure a Certificate Authority (Microsoft CA or OpenSSL) in VCF Operations for a VCF Instance
  • Replace default VMCA-signed certificates of vCenter, NSX and SDDC Manager with CA-signed certificates from VCF Operations (Generate CSR → Replace With Configured CA Certificate)
  • Activate auto-renewal for non-disruptive certificate updates and monitor certificate alerts
  • Troubleshoot certificate trust-chain issues
  • Document the certificate lifecycle process; know where the vCenter certificate-manager CLI still fits (outside VCF-managed lifecycle)

Prerequisites

VCF 9.0 Instance operational with VCF Operations fleet management; a Microsoft Certificate Authority with the Certificate Authority and Web Enrollment roles on the same server and a VMware-style issuing template (or OpenSSL on the SDDC Manager appliance for a lab CA); a VCF Operations user with the Administrator role

Required skills:

  • PKI/certificate concepts
  • vCenter Certificate Manager
  • OpenSSL basics

Lab Environment

VCF 9.0 with VCF Operations, SDDC Manager, vCenter, NSX Manager cluster and 2+ ESX hosts. Enterprise CA (AD CS with Web Enrollment) reachable from VCF Operations and time-synchronised with SDDC Manager; OpenSSL on SDDC Manager as the lab alternative (VCF Instance components only — VCF Management components support Microsoft CA only).

Tasks

Task 1 CA-Signed Certificate Replacement and Auto-Renewal from VCF Operations

In VCF 9.0 the certificate lifecycle of SDDC Manager, NSX Local Manager/VIP, vCenter machine SSL, ESX SSL and VCF Identity Broker is owned by VCF Operations (Fleet Management > Certificates): view certificates and alerts, configure a CA, generate CSRs, replace certificates, and activate auto-renewal for certificates issued by VMCA, Microsoft CA or OpenSSL CA with non-disruptive updates. The SDDC Manager UI and API for certificate management are deprecated in favour of it. The VCF design recommendation is to replace the default VMCA-signed certificates with certificates signed by an internal CA. Re-rooting VMCA with the vCenter certificate-manager CLI is a vSphere-only procedure that bypasses the VCF-managed workflow; keep it out of VCF-managed estates and never run it during VCF lifecycle operations.

Move the VCF Instance from default VMCA-signed certificates to enterprise CA-signed certificates using the VCF 9.0 workflow — Certificate Authority configured in VCF Operations, CSR generation and replacement per component, auto-renewal switched on — the certificate operation a VCF administrator performs in production.

Step 1

Pre-flight: audit the current certificate state. VCF Operations → Fleet Management → Certificates → VCF Management (VCF Operations, fleet components) and VCF Instances → <instance> (SDDC Manager, vCenter, NSX; toggle Show ESX Hosts). Note issuer (VMCA/self-signed), expiry and any certificate alerts. Cross-check on vCenter if you wish: /usr/lib/vmware-vmafd/bin/vecs-cli store list and vecs-cli entry list --store MACHINE_SSL_CERT --text | grep -A2 Validity.

Inventory of components, issuers and expiry dates; alerts noted.
Step 2

Configure the Certificate Authority for the VCF Instance. Fleet Management → Certificates → VCF Instances → <instance> → Configure CA. Microsoft CA: CA Server URL https://<ca-fqdn>/certsrv, a least-privileged service account, the issuing Template Name (for example VMware) created on the CA; prerequisites are the CA + Web Enrollment roles on the same server, connectivity from VCF Operations and NTP alignment with SDDC Manager. Lab alternative: OpenSSL (Common Name = SDDC Manager FQDN, country, locality, organisation…). Save. VCF Management components accept Microsoft CA only; VCF Instance components accept Microsoft CA or OpenSSL.

CA shown as configured for the VCF Instance.
Step 3

Generate the CSR for vCenter. VCF Instances → <instance> → select the vCenter row → three-dot menu → Generate CSR. Enter Common Name (FQDN), Organization, Organizational Unit, Locality, State, Country, key size (ESX hosts allow 2048 bit only). Save and wait until the CSR is generated. Repeat for the NSX Manager (LM + VIP) and SDDC Manager rows.

CSR status successful for vCenter, NSX and SDDC Manager.
Step 4

Replace with the configured CA certificate. For each component: three-dot menu → Replace With Configured CA Certificate → select the CA → Confirm. VCF Operations submits the CSR to the Microsoft CA (or signs with OpenSSL), installs the certificate and restarts what is needed; follow the task until it completes before moving to the next component. External-CA variant (no CA configured in VCF Operations): Generate CSR → download → sign externally → import the signed certificate (chain validated on upload) → Replace With Imported Certificate.

Issuer column shows the enterprise CA for vCenter, NSX and SDDC Manager; no failed tasks.
Step 5

Verify the trust chain. Browse to the vCenter and NSX UIs — the browser shows a trusted certificate when the enterprise root is in its trust store. From a shell: openssl s_client -connect <vcenter-fqdn>:443 -showcerts | openssl x509 -noout -issuer -subject -dates; the chain must terminate at the enterprise root with no untrusted intermediate.

Issuer = enterprise issuing CA; chain verifies; browser padlock trusted.
Step 6

Renew ESX host certificates. In VCF Operations, toggle Show ESX Hosts, select the hosts and either Renew (VMCA-issued) or Generate CSR → Replace With Configured CA Certificate (CA-signed, 2048-bit key). Hosts stay operational; no reboot. Manual renewal is also available for VMCA, Microsoft CA, OpenSSL or self-signed certificates (root certificates cannot be renewed).

All hosts show renewed certificates with new expiry dates.
Step 7

Activate auto-renewal. Fleet Management → Certificates → VCF Instances → <instance> → Activate Auto-renewal toggle → review → Confirm (the status can take a while to appear). Auto-renewal applies to the certificates VCF Operations manages for non-disruptive updates: ESX SSL, vCenter machine SSL, NSX LM and VIP, SDDC Manager SSL, VCF Identity Broker. Certificate expiry notifications are raised across the VCF infrastructure; add a VCF Operations alert notification rule so the certificate alerts reach the security team.

Auto-renewal Active for the instance; certificate alert notifications routed.
Step 8

Test certificate trust from clients. (a) curl -v https://<vcenter-fqdn>/ — TLS handshake without warnings; (b) PowerCLI Connect-VIServer <vcenter> — connects without ignoring certificate errors; (c) REST: curl https://<vcenter>/api/session -u user — no -k needed. Any failure points at a missing intermediate in the client trust store or at a component that still carries its VMCA certificate.

Clients connect without certificate overrides.
Step 9

Document the certificate lifecycle runbook: (a) CA configuration in VCF Operations (per VCF Instance; separate CA configuration for VCF Management components); (b) which certificates are auto-renewed and the expiry alert thresholds; (c) the manual renewal / CSR-and-replace procedure for exceptions and external CAs; (d) the trust chain (issuing CA, root, expiry); (e) emergency replacement for a compromised certificate.

Runbook stored with the design documentation.
Step 10

Reference only — the vSphere certificate-manager CLI. /usr/lib/vmware-vmca/bin/certificate-manager on the vCenter appliance (replace the VMCA root with a custom signing certificate, reset all certificates) is the vSphere-native path for estates that are not VCF-managed. In a VCF 9.0 estate it bypasses VCF Operations' inventory and auto-renewal and must not be run during VCF lifecycle operations; use it only under Broadcom Support direction.

Understood where the CLI path applies and why it is not used here.

Validation Gate

Check: CA-signed certificates in place and auto-renewal active via VCF Operations

Expected: CA configured for the VCF Instance; vCenter, NSX and SDDC Manager certificates replaced with enterprise CA-signed certificates; ESX certificates renewed; chain verifies from clients; auto-renewal active and certificate alerts routed

Common Errors

Replace With Configured CA Certificate fails against the Microsoft CA
Fix: Check the three CA prerequisites: Certificate Authority and Web Enrollment roles on the same server, HTTPS connectivity from VCF Operations to https://<ca>/certsrv, NTP alignment between the CA and SDDC Manager; confirm the Template Name exists and the service account may enrol with it.
Imported external certificate fails validation
Fix: The upload must contain the signed certificate matching the CSR generated in VCF Operations plus the full chain (intermediates to root) in PEM; verify with openssl verify -CAfile chain.pem signed.crt before importing.
Clients still see an untrusted certificate after replacement
Fix: Either the client lacks the enterprise root/intermediate in its trust store, or you replaced the vCenter certificate but are connecting to a component (NSX VIP, SDDC Manager) still on VMCA — check each row's issuer under Fleet Management → Certificates.
Auto-renewal status not shown after activation
Fix: The status can take some time to appear in the console; refresh later. Auto-renewal for Microsoft CA/OpenSSL certificates also requires a configured CA for that VCF Instance.

Final Validation

Certificate lifecycle management operational through VCF Operations with enterprise CA integration

✓ CA configured → Microsoft CA or OpenSSL configured for the VCF Instance under Fleet Management → Certificates

✓ Replacement → vCenter, NSX and SDDC Manager issuers show the enterprise CA

✓ ESX certificates → All hosts renewed with new expiry dates

✓ Trust → Browser and CLI clients connect without certificate overrides

✓ Auto-renewal → Auto-renewal active; certificate alert notifications configured

Cleanup / Restore

• Keep the CA-signed certificates and auto-renewal in place

• Document the certificate chain in the CMDB

• Review certificate alerts monthly

Design Reflection (VCDX)

Certificate management is a frequent VCDX defence topic. Key arguments: (1) VCF 9.0 centralises certificate lifecycle in VCF Operations — one inventory, one CA integration, auto-renewal with non-disruptive updates — so the design names the CA (Microsoft CA for management components; Microsoft CA or OpenSSL for instance components), the template and the renewal policy rather than per-product CLIs; (2) certificate expiry is a leading cause of VCF service outages, so alerts and auto-renewal are availability controls; (3) the trust chain and the exception procedure (external CA, imported certificates) are operational deliverables.

Requirements

  • Enterprise-trusted certificates on all VCF management interfaces
  • Proactive expiry monitoring with 60-day warning
  • Annual certificate rotation capability without service outage

Constraints

  • VCF Management components support Microsoft CA only; VCF Instance components support Microsoft CA or OpenSSL
  • Microsoft CA needs the CA and Web Enrollment roles on one server, reachable from VCF Operations, time-synchronised with SDDC Manager
  • ESX host certificates use 2048-bit keys only; root certificates cannot be renewed

Assumptions

  • Enterprise CA (Microsoft CA with Web Enrollment) is reachable from VCF Operations and has a VMware issuing template
  • Enterprise root CA is in all client trust stores (browsers, API tools)
  • Certificate operations are run outside VCF lifecycle operations

Risks

  • A failed replacement task leaves one component on its old certificate — re-run from Fleet Management → Certificates; VCF Operations keeps the inventory consistent
  • Expired enterprise root or issuing CA invalidates the whole VCF certificate chain
  • Certificate replacement without updating external integrations (monitoring, backup) causes their trust checks to fail

Self-Assessment Discussion Prompts

  1. When would you import externally signed certificates instead of configuring a CA in VCF Operations?
  2. How do you handle certificate renewal in a VCF Instance with 10+ vCenters — what does auto-renewal cover and what stays manual?
  3. What is the blast radius of an expired issuing CA certificate across the VCF components?

Extensions

Automate CSR/replace sequences with the VCF Operations certificate APIs (the SDDC Manager certificate API is deprecated)

Configure OpenSSL on SDDC Manager as the lab CA for the VCF Instance and compare the workflow with Microsoft CA

Build a VCF Operations dashboard listing all certificate expiry dates and alerts

⚠ Known Pitfalls

Re-rooting VMCA with the vCenter certificate-manager CLI in a VCF-managed estate — it bypasses VCF Operations certificate management and must never run during VCF lifecycle operations
Installing the Microsoft CA Web Enrollment role on a different server from the CA role — VCF Operations cannot request and sign certificates automatically
Configuring OpenSSL for VCF Management components — only Microsoft CA is supported there; OpenSSL is for VCF Instance components
Forgetting the ESX hosts (hidden by default behind the Show ESX Hosts toggle) when replacing or auto-renewing

References

  • VCF 9.0 documentation — Managing Certificates in VMware Cloud Foundation; Configure a Certificate Authority; Replace a Certificate with a CA-Signed Certificate; Replace a Certificate with an External CA-Signed Certificate; Activate Auto-renewal: https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0.html
  • VCF 9.0 documentation — Certificate Management Design (replace default VMCA-signed certificates with internal CA-signed certificates): https://techdocs.broadcom.com/us/en/vmware-cis/vcf/vcf-9-0-and-later/9-0.html
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.