The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
This chapter includes the following sections:
Organizational units (OUs) in the AD server contain AD groups that map to user roles in Cisco UCS. For every role maintained in AD, you must have the same role configured in Cisco UCS.
Note | Maintaining matching role names in both AD and Cisco UCS is a requirement for integration. |
Create a non-admin bind user and add it to the CiscoUCS OU.
Cisco UCS uses the non-admin bind user account to regularly check which groups the user is included in within the AD server.
Note | To prevent unnecessary authentication errors, we recommend that this account be set up with a non-expiring password. |
A user account called ucsbind appears in the CiscoUCS OU.
What to Do Next
Create sample users and add them to the CiscoUCS OU.
Collect information needed for the Cisco UCS LDAP configuration.
To configure LDAP and multiple simultaneous authorizations in Cisco UCS Manager, you need to access several values from the AD server. This example uses ADSI Edit, a free third-party utility, to find the required values.
Install and configure ADSI Edit.
Configure Cisco UCS using these values.