Users Guide

database. Some example user class attributes can include the 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 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 defined with a unique ID. To maintain unique IDs
across the industry, Microsoft maintains a database of Active Directory Object Identifiers (OIDs) so that when companies add extensions
to the schema, they can be guaranteed to be unique and not to conflict 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:
• Extension is: dell
• Base OID is: 1.2.840.113556.1.8000.1280
• RAC LinkID range is: 12070 to 12079
Overview of iDRAC 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 specific set of privileges to one or more iDRAC devices. This model provides an administrator maximum
flexibility over the different combinations of users, iDRAC privileges, and iDRAC devices on the network without much complexity.
For each physical iDRAC device on the network that you want to integrate with Active Directory for authentication and authorization,
create at least one association object and one iDRAC device object. You can create multiple association objects, and each association
object can be linked to as many users, groups of users, or iDRAC device objects as required. The users and iDRAC user groups can be
members of any domain in the enterprise.
However, each association object can be linked (or, may link users, groups of users, or iDRAC device objects) to only one privilege object.
This example allows an administrator to control each user’s privileges on specific iDRAC devices.
iDRAC device object is the link to iDRAC firmware for querying Active Directory for authentication and authorization. When iDRAC is
added to the network, the administrator must configure iDRAC and its device object with its Active Directory name so that users can
perform authentication and authorization with Active Directory. Additionally, the administrator must add iDRAC to at least one association
object for users to authenticate.
The following figure shows that the association object provides the connection that is needed for the authentication and authorization.
Figure 2. Typical Setup for Active Directory Objects
You can create as many or as few association objects as required. However, you must create at least one Association Object, and you
must have one iDRAC Device Object for each iDRAC device on the network that you want to integrate with Active Directory for
Authentication and Authorization with iDRAC.
The Association Object allows for as many or as few users and/or groups as well as iDRAC Device Objects. However, the Association
Object only includes one Privilege Object per Association Object. The Association Object connects the Users who have Privileges on
iDRAC devices.
The Dell extension to the ADUC MMC Snap-in only allows associating the Privilege Object and iDRAC Objects from the same domain with
the Association Object. The Dell extension does not allow a group or an iDRAC object from other domains to be added as a product
member of the Association Object.
When adding Universal Groups from separate domains, create an Association Object with Universal Scope. The Default Association
objects created by the Dell Schema Extender Utility are Domain Local Groups and does not work with Universal Groups from other
domains.
Users, user groups, or nested user groups from any domain can be added into the Association Object. Extended Schema solutions support
any user group type and any user group nesting across multiple domains allowed by Microsoft Active Directory.
Configuring User Accounts and Privileges
121