Replacing a certificate in VCF Operations via API results in the error message: "external CA does not exist." when using external as the caType

Products

• VCF Operations

Issue/Introduction

Replacing a TLS certificate for VCF management components using an externally signed certificate in the VCF Operations UI is successful.

Replacing the certificate via API with the call "/lcm/locker/api/v3/certificates/{caType}/replace" fails with an error when entering 'external' as the caType:

external CA does not exist

Environment

VCF Operations 9.x

Resolution

The only currently supported option for caType when replacing a certificate via API is 'msca'

/lcm/locker/api/v3/certificates/msca/replace