|
racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog2 name or IP address of the domain controller>racadm config -g cfgActiveDirectory -o cfgADGlobalCatalog3 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 groupsare in different domains. In multiple domain case, only the Universal Group can be used.NOTE: The FQDN or IP address that you specify in this field should match the Subject or Subject AlternativeName field of your domain controller certificate if you have certificate validation enabled.If you want to disable the certificate validation during the SSL handshake, run the following RACADM command:• Using the config command: racadm config -g cfgActiveDirectory -o cfgADCertValidationEnable 0In this case, you do not have to upload the Certificate Authority (CA) certificate.To enforce the certificate validation during SSL handshake (optional):• Using the config command: racadm config -g cfgActiveDirectory -o cfgADCertValidationEnable 1In this case, you must upload the CA certificate using the following RACADM command:racadm sslcertupload -t 0x2 -f NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the Global CatalogFQDN. Make sure that DNS is correctly configured.Extended Schema Active Directory OverviewUsing the extended schema solution requires the Active Directory schema extension.Active Directory Schema ExtensionsThe Active Directory data is a distributed database of attributes and classes. The Active Directory schema includes the rules thatdetermine the type of data that can be added or included in the database. One example of a class that is stored in the database isthe user class. Some example user class attributes are user’s first name, last name, phone number, and so on.You can extend the Active Directory database by adding your own unique attributes and classes for specific requirements. Dell hasextended the schema to include the necessary changes to support remote management authentication and authorization usingActive Directory.Each attribute or class that is added to an existing Active Directory Schema must be defined with a unique ID. To maintain unique IDsacross the industry, Microsoft maintains a database of Active Directory Object Identifiers (OIDs), so that when companies addextensions to the schema, they can be guaranteed to be unique and not to conflict with each other. To extend the schema inMicrosoft's Active Directory, Dell received unique OIDs, unique name extensions, and uniquely linked attribute IDs for the attributesand 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 12079Overview of Schema ExtensionsDell has extended the schema to include an Association, Device, and Privilege property. The Association property is used to linktogether the users or groups with a specific set of privileges to one or more RAC devices. This model provides an administratormaximum flexibility over the different combinations of users, RAC privileges, and RAC devices on the network without muchcomplexity.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, andeach association object can be linked to as many users, groups of users, or RAC device objects as required. The users and RACdevice 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 privilegeobject. This example allows an administrator to control each user’s privileges on specific CMCs.The RAC device object is the link to RAC firmware for querying Active Directory for authentication and authorization. When a RAC isadded to the network, the administrator must configure the RAC and its device object with its Active Directory name so that users120
|
