Deploying VMware Identity broker 9.1 without clean up of existing VMware Identity broker 9.0.x.

Products

• VCF Operations

Issue/Introduction

VMware Identity broker 9.1 component is re-deployed without properly cleaning up the existing VMware Identity broker 9.0.x. In this situation errors similar to the following are observed in the adapter logs.

/storage/log/vcops/log/adapters/ManagementAdapter/ManagementAdapter.log

com.vmware.adapter.management.components.iam.exception.HttpResponseStatusException: API call https://<external-vidb-fqdn>/acs/t/CUSTOMER/token failed with status 401 and error {"error":"invalid_client","error_description":"Client is not authorized to perform this operation."}
        at com.vmware.adapter.management.components.iam.client.ApiInvoker.invoke(ApiInvoker.java:87)
        at com.vmware.adapter.management.components.iam.client.ApiInvoker.invoke(ApiInvoker.java:50)
        at com.vmware.adapter.management.components.iam.client.token.ExternalVidbTokenClient.getTenantAdminToken(ExternalVidbTokenClient.java:101)
        at com.vmware.adapter.management.components.iam.client.ApiClientProvider.getApiClient(ApiClientProvider.java:130)

Environment

• VCF Operations 9.1
• VMware Identity broker 9.1

Cause

This issue occurs because the CUSTOMER tenant structure is not successfully created during the VIDB component registration process. Due to the missing tenant configuration, VCF Operations cannot establish communication with the external VIDB instance.

Resolution

Follow the instructions in the following KB to delete the corrupted VMware Identity broker component.

Script to delete the existing VCF Identity Broker 9.0.x from VCF Operations 9.1