Non-Disruptive Certificate Flow Fails When a Component's Certificate Is Replaced or Renewed Twice
search cancel

Non-Disruptive Certificate Flow Fails When a Component's Certificate Is Replaced or Renewed Twice

book

Article ID: 401865

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

If a certificate on any VCF Management Component is updated twice, whether through its native UI, API, or CLI, the trust cannot be established between the component and VCF Operations fleet management.

Non-Disruptive Certificate (NDC) flow supports only a single direct certificate update on the component

Environment

VCF Operations 9.0

Resolution

We have to manual establish the trust on VCF Operations fleet management by triggering this API.

curl --location --request POST 'https://<lcm-fqdn>/lcm/certificate-management/api/certificate-trust?endpoint=<endpoint to be trusted>' \
--header 'Authorization: Basic <basic-auth>'

endpoint to be trusted is the component URL where the certificate has been changed more than once.