Set up vCenter identity sources to use Active Directory

आलेख
08/15/2019

About VMware vCenter identity sources

VMware vCenter supports different identity sources for authentication of users who access vCenter. Your CloudSimple Private Cloud vCenter can be set up to authenticate with Active Directory for your VMware administrators to access vCenter. When the setup is complete, the cloudowner user can add users from the identity source to vCenter.

You can set up your Active Directory domain and domain controllers in any of the following ways:

Active Directory domain and domain controllers running on-premises
Active Directory domain and domain controllers running on Azure as virtual machines in your Azure subscription
New Active Directory domain and domain controllers running in your Private Cloud
Azure Active Directory service

This guide explains the tasks to set up Active Directory domain and domain controllers running either on-premises or as virtual machines in your subscriptions. If you would like to use Azure AD as the identity source, refer to Use Azure AD as an identity provider for vCenter on CloudSimple Private Cloud for detailed instructions in setting up the identity source.

Before adding an identity source, temporarily escalate your vCenter privileges.

Caution

New users must be added only to Cloud-Owner-Group, Cloud-Global-Cluster-Admin-Group, Cloud-Global-Storage-Admin-Group, Cloud-Global-Network-Admin-Group or, Cloud-Global-VM-Admin-Group. Users added to Administrators group will be removed automatically. Only service accounts must be added to Administrators group and service accounts must not be used to sign in to vSphere web UI.

Identity source options

Add on-premises Active Directory as a single sign-on identity source
Set Up New Active Directory on a Private Cloud
Set Up Active Directory on Azure

Important

Active Directory (Windows Integrated Authentication) is not supported. Only Active Directory over LDAP option is supported as an identity source.

Add On-Premises Active Directory as a Single Sign-On Identity Source

To set up your on-premises Active Directory as a Single Sign-On identity source, you need:

Site-to-Site VPN connection from your on-premises datacenter to your Private Cloud.
On-premises DNS server IP added to vCenter and Platform Services Controller (PSC).

Use the information in the following table when setting up your Active Directory domain.

Option	Description
Name	Name of the identity source.
Base DN for users	Base distinguished name for users.
Domain name	FQDN of the domain, for example, example.com. Do not provide an IP address in this text box.
Domain alias	The domain NetBIOS name. Add the NetBIOS name of the Active Directory domain as an alias of the identity source if you are using SSPI authentications.
Base DN for groups	The base distinguished name for groups.
Primary Server URL	Primary domain controller LDAP server for the domain. Use the format `ldap://hostname:port` or `ldaps://hostname:port`. The port is typically 389 for LDAP connections and 636 for LDAPS connections. For Active Directory multi-domain controller deployments, the port is typically 3268 for LDAP and 3269 for LDAPS. A certificate that establishes trust for the LDAPS endpoint of the Active Directory server is required when you use `ldaps://` in the primary or secondary LDAP URL.
Secondary server URL	Address of a secondary domain controller LDAP server that is used for failover.
Choose certificate	If you want to use LDAPS with your Active Directory LDAP Server or OpenLDAP Server identity source, a Choose certificate button appears after you type `ldaps://` in the URL text box. A secondary URL is not required.
Username	ID of a user in the domain who has a minimum of read-only access to Base DN for users and groups.
Password	Password of the user who is specified by Username.

When you have the information in the previous table, you can add your on-premises Active Directory as a Single Sign-On identity source on vCenter.

Tip

You'll find more information on Single Sign-On identity sources on the VMware documentation page.

Set Up new Active Directory on a Private Cloud

You can set up a new Active Directory domain on your Private Cloud and use it as an identity source for Single Sign-On. The Active Directory domain can be a part of an existing Active Directory forest or can be set up as an independent forest.

New Active Directory forest and domain

To set up a new Active Directory forest and domain, you need:

One or more virtual machines running Microsoft Windows Server to use as domain controllers for the new Active Directory forest and domain.
One or more virtual machines running DNS service for name resolution.

See Install a New Windows Server 2012 Active Directory Forest for detailed steps.

Tip

For high availability of services, we recommend setting up multiple domain controllers and DNS servers.

After setting up the Active Directory forest and domain, you can add an identity source on vCenter for your new Active Directory.

New Active Directory domain in an existing Active Directory forest

To set up a new Active Directory domain in an existing Active Directory forest, you need:

Site-to-Site VPN connection to your Active Directory forest location.
DNS Server to resolve the name of your existing Active Directory forest.

See Install a new Windows Server 2012 Active Directory child or tree domain for detailed steps.

After setting up the Active Directory domain, you can add an identity source on vCenter for your new Active Directory.

Set up Active Directory on Azure

Active Directory running on Azure is similar to Active Directory running on-premises. To set up Active Directory running on Azure as a Single Sign-On identity source on vCenter, the vCenter server and PSC must have network connectivity to the Azure Virtual Network where Active Directory services are running. You can establish this connectivity using Azure Virtual Network Connection using ExpressRoute from the Azure virtual network where Active Directory Services are running to CloudSimple Private Cloud.

After the network connection is established, follow the steps in Add On-Premises Active Directory as a Single Sign-On Identity Source to add it as an Identity Source.