Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Configuring Active Directory for VMware vCloud Request Manager (1031066)

Last Updated: 11/25/2010Categories: Total Views: 5798Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides the prerequisites and procedures to configure Active Directory to support VMware vCloud Request Manager.

Resolution

VMware vCloud Request Manager populates its users by accessing the same Microsoft Active Directory domain that is used by VMware vCloud Director. Therefore vCloud Request Manager server should be located within that same domain, having access to the same Microsoft Active Directory domain that is used by VMware vCloud Director.

vCloud Request Manager Active Directory integration requires an existing single group or organization unit within the directory that contains every user that plans to use vCloud Request Manager. For example, if all the required users reside in the Engineering organizational unit (OU) you could enter LDAP://.../OU=Engineering,dc=mydomain,dc=com for the connection string.

You need to check that the User <> Manager relationship is established in Active Directory.

Note: vCloud Request Manager does not recognize users that have been manually created as local users in vCloud Director. It only recognises those users that have been imported from the Active Directory server.

Ensure that you meet these prerequisites for configuring Active Directory for vCloud Request Manager:

You have vCloud Administrator privileges

vCloud Request Manager has access to the Active Directory source

vCloud Request Manager is connected to a specific domain controller, not just a domain

During the installation of vCloud Request Manager, you created an Active Directory source. You can use the vCloud Request Manager Admin Portal to reconfigure your Active Directory settings.

To configure Active Directory:

Log in to the Request Manager Admin Portal.

Click Integration.

Click Sources on the Main tab in the left explorer panel.

Select Active Directory and click the Select External Source button.

Enter or modify the settings for the Active Directory source.

Type a name to identify the Active Directory source.

Select a status for the source.

Select Active to use the source throughout Request Manager.

Select Inactive to disable the source throughout Request Manager.

Type the full LDAP server path of the Active Directory server. This must include the protocol, server, and root naming context and can optionally include a port number or a group of users. For example:

LDAP://myldapserver.mydomain.com:port/OU=mygroup/dc=mydomain,dc=com

ldap://dc=mydomain,dc=com/

Note: You must use capital letters for the LDAP prefix. For LDAP over SSL, type LDAP:// for the server path and choose SSL.

Type the user DN/ID.

This is the Windows account used to connect to the Active Directory server. You can type the user principal name (for example login@domain), or the flat domain name (for example, domain\user). If you do not provide a User DN/ID, the connector uses the credentials of the executing accounts, in this case the Web server and Integration service. Ensure that both these accounts have appropriate rights.

Type the password used to authenticate the user.

If the connection string provides a specific server, select Server Bind for optimal performance. Do not select this option for serverless connection strings.

If the connection to Active Directory uses SSL, select SSL. To use SSL, the Active Directory security certificate must be installed in the Trusted Root Certification Authorities > Local Computer folder.

Select Kerberos/NTLM to use Kerberos/NTLM to authenticate the connection.

Type the NT Domain Name of the Active Directory Server.

Select Authenticate Imported People against Source to authenticate users logging into the Request Manager User Portal with their Active Directory credentials. This options uses AD credentials and not the credential defined within Request Manager.

Click Test.

Click Save.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Request Manager

Related Versions:

VMware vCloud Request Manager 1.0.x

Take Our Survey

Support Assistant