[VMC on AWS] Cannot configure vsphere.local as Identity Source to link to Cloud vCenter while deploying vCenter Cloud Getaway

Products

• VMware Cloud on AWS

Issue/Introduction

Symptoms:

• When configuring vsphere.local as Identity Source while deploying vCenter Cloud Getaway, you cannot see vsphere.local in the pull down.

 

Resolution

Is is expected behavior in vCenter Cloud Gataway released with SDDC 1.11 and the later release.
vsphere.local is not supported to configure as identity source for Hybrid linked Mode linking anymore.


Please choose your AD domain as Identity Source to link to Cloud vCenter.