Users Guide
racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog2 <fully qualified domain
name or IP address of the domain controller>
racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog3 <fully qualified domain
name or IP address of the domain controller>
NOTE: The Global Catalog server is only required for standard schema when the user accounts and role groups
are in dierent domains. In multiple domain case, only the Universal Group can be used.
NOTE: The FQDN or IP address that you specify in this eld should match the Subject or Subject Alternative
Name eld of your domain controller certicate if you have certicate validation enabled.
If you want to disable the certicate validation during the SSL handshake, run the following RACADM command:
• Using the cong command: racadm config -g cfgActiveDirectory -o cfgADCertValidationEnable 0
In this case, you do not have to upload the Certicate Authority (CA) certicate.
To enforce the certicate validation during SSL handshake (optional):
• Using the cong command: racadm config -g cfgActiveDirectory -o cfgADCertValidationEnable 1
In this case, you must upload the CA certicate using the following RACADM command:
racadm sslcertupload -t 0x2 -f <ADS root CA certificate>
NOTE: If certicate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog
FQDN. Make sure that DNS is correctly congured.
Extended Schema Active Directory Overview
Using the extended schema solution requires the Active Directory schema extension.
Active Directory Schema Extensions
The Active Directory data is a distributed database of attributes and classes. The Active Directory schema includes the rules that
determine the type of data that can be added or included in the database. One example of a class that is stored in the database is
the user class. Some example user class attributes are user’s rst name, last name, phone number, and so on.
You can extend the Active Directory database by adding your own unique attributes and classes for specic requirements. Dell has
extended the schema to include the necessary changes to support remote management authentication and authorization using
Active Directory.
Each attribute or class that is added to an existing Active Directory Schema must be dened with a unique ID. To maintain unique IDs
across the industry, Microsoft maintains a database of Active Directory Object Identiers (OIDs), so that when companies add
extensions to the schema, they can be guaranteed to be unique and not to conict with each other. To extend the schema in
Microsoft's Active Directory, Dell received unique OIDs, unique name extensions, and uniquely linked attribute IDs for the attributes
and classes that are added into the directory service.
• Dell extension: dell
• Dell base OID: 1.2.840.113556.1.8000.1280
• RAC LinkID range: 12070 to 12079
Overview of Schema Extensions
Dell has extended the schema to include an Association, Device, and Privilege property. The Association property is used to link
together the users or groups with a specic set of privileges to one or more RAC devices. This model provides an administrator
maximum exibility over the dierent combinations of users, RAC privileges, and RAC devices on the network without much
complexity.
When there are two CMCs on the network that you want to integrate with Active Directory for authentication and authorization,
create at least one association object and one RAC device object for each CMC. You can create multiple association objects, and
each association object can be linked to as many users, groups of users, or RAC device objects as required. The users and RAC
device objects can be members of any domain in the enterprise.
However, each association object can be linked (or, may link users, groups of users, or RAC device objects) to only one privilege
object. This example allows an administrator to control each user’s privileges on specic CMCs.
The RAC device object is the link to RAC rmware for querying Active Directory for authentication and authorization. When a RAC is
added to the network, the administrator must congure the RAC and its device object with its Active Directory name so that users
120