[VMC on AWS] Unable to add on-premises Active Directory over LDAP as an identity source when linking from Cloud SDDC
search cancel

[VMC on AWS] Unable to add on-premises Active Directory over LDAP as an identity source when linking from Cloud SDDC

book

Article ID: 327101

calendar_today

Updated On:

Products

VMware Cloud on AWS

Issue/Introduction

This article provides information why you are unable to add on-premises Active Directory over LDAP as an identity source for the SDDC vCenter Server.

Symptoms:
Unable to add on-premises Active Directory over LDAP as an identity source for the SDDC vCenter Server.

Error message:
Failed to probe provider connectivity [URI: ldaps://xxx.xxx.xxx:636]; tenantName [vmc.local], userName [xxxxx] Caused by: Can't contact LDAP server

Cause

An on-premises DNS server is not configured for your management gateway on SDDC so that it can resolve the FQDN for the identity source.

Resolution

Ensure that an on-premises DNS server is configured for your management gateway on SDDC using VMC console. To get started with the DNS configuration, refer the operations guide on how to Configure DNS Services. Also ensure that you have met the prerequisites in Hybrid Linked Mode Prerequisites.

Powered by Wolken Software