Figure 6: Active Directory identity source Figure 5: Configure an Active Directory identity source with default parametersĪfter closing the previous dialog with OK, you should see the new identity source (See Figure 6). Unfortunately we will soon see that we are let down with this expectation.įor now select as the Identity source type the value Active Directory (Integrated Windows Authentication), confirm your domain name and select Use machine account (See Figure 5). In the end, that’s why we added vCSA to the Active Directory in the first place. Figure 4: Add a new SSO Identity SourceĪs the vCSA is already joined to the Active Directory domain the expectation would be to use the Integrated Windows Authentication for Active Directory along with using the vCSA machine account. Next, try to create a new Identity Source (See Figure 4). Figure 3: Navigate to Administration -> Single Sign-On -> Configuration Navigate to Home -> Administration -> Single Sign-On -> Configuration (See Figure 3). Figure 2: Login to vCSA with the SSO administrator credentials Note that this account is different from the user root. Login with the vCSA SSO credentials It has a default password of vmware (See Figure 2). Figure 1: VMware vCenter Server Appliance with Active Directory integration enabled We start with the VMware vCenter Server Appliance (vCSA) joined to the Active Directory (See Figure 1). In a subsequent step you will then see how to prevent it. The following steps show you how to reproduce the error. This article will show you how to work around this issue and still use Active Directory with your vCSA. While attempting to integrate the VMware vSphere 5.5 vCenter Server Appliance (vCSA) with Microsoft Active Directory you might have stumbled over the error message “Error: Idm client exception: Failed to establish server connection”.

Handling the VMware vSphere 5.5 Active Directory integration error

Idm error code 5