VMCA Signed Certificates Incorrectly Labeled as "External CA" in VCF Operations 9.1

Products

• VCF Operations

Issue/Introduction

In the VCF Operations 9.1 Certificate Management dashboard, vCenter Server instances using certificates signed by the internal VMware Certificate Authority (VMCA) are inconsistently identified.

• Some ESXi or vCenter instances correctly display the status as "VMCA" while certain  other instances are listed with 'External CA' certificate, even though the certificates are VMCA-signed.
• In VCF Operations, certificate type is reported as 'External CA' even though the certificate details list default certificates signed by VMCA:
  
  
  • Certificate details for one of the ESX hosts from vCenter(vCenter > Select the host > Configure > Under System, click Certificate):
    
    
  • Certificate type for ESX host in VCF Operations
    
    
    
    
  • Certificate Details for the ESX host:
    
    

Environment

VCF Operations 9.1

Cause

This is a known issue where the VMCA self-signed root certificate is collected as External CA instead of Self signed in  VCF Operations 9.1 

Resolution

To resolve this issue, upgrade to VCF Operations 9.1.1. 

Starting with VCF Operations 9.1.1, VCF Operations detects and displays component self-signed CAs and self-signed CA certificates as self-signed in the VCF Operations UI. For more information, refer  VCF Operations detects and displays self-signed .