Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 131

Extended schema Active Directory overview, Active directory schema extensions

Page 131 highlights

In this case, you must upload the CA certificate using the following command: racadm sslcertupload -t 0x2 -f NOTE: If certificate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog FQDN. Ensure that DNS is configured correctly under Overview > iDRAC Settings > Network. Using the following RACADM command may be optional. racadm sslcertdownload -t 1 -f 2. If DHCP is enabled on iDRAC and you want to use the DNS provided by the DHCP server, enter the following command: racadm set iDRAC.IPv4.DNSFromDHCP 1 3. If DHCP is disabled on iDRAC or you want manually enter the DNS IP address, enter the following RACADM command: racadm set iDRAC.IPv4.DNSFromDHCP 0 racadm set iDRAC.IPv4.DNSFromDHCP.DNS1 racadm set iDRAC.IPv4.DNSFromDHCP.DNS2 4. If you want to configure a list of user domains so that you only need to enter the user name when logging in to the web interface, use the following command: racadm set iDRAC.UserDomain..Name You can configure up to 40 user domains with index numbers between 1 and 40. Extended schema Active Directory overview Using the extended schema solution requires the Active Directory schema extension. Best practices for extended schema The extended schema uses Dell association objects to join iDRAC and permission. This allows you to use iDRAC based on the overall permissions granted. The default Access Control List (ACL) of Dell Association objects allows Self and Domain Administrators to manage the permissions and scope of iDRAC objects. By default, the Dell Association objects do not inherit all permissions from the parent Active Directory objects. If you enable inheritance for the Dell Association object, the inherited permissions for that association object are granted to the selected users and groups. This may result in unintended privileges being provided to the iDRAC. To use the Extended Schema securely, Dell recommends not enabling inheritance on Dell Association objects within the extended schema implementation. 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. The user class is one example of a class that is stored in the 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 Configuring user accounts and privileges 131

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

In this case, you must upload the CA certificate using the following command:
racadm sslcertupload -t 0x2 -f <ADS root CA certificate>
NOTE:
If certificate validation is enabled, specify the Domain Controller Server addresses and the Global Catalog
FQDN. Ensure that DNS is configured correctly under Overview > iDRAC Settings > Network.
Using the following RACADM command may be optional.
racadm sslcertdownload -t 1 -f <RAC SSL certificate>
2.
If DHCP is enabled on iDRAC and you want to use the DNS provided by the DHCP server, enter the following command:
racadm set iDRAC.IPv4.DNSFromDHCP 1
3.
If DHCP is disabled on iDRAC or you want manually enter the DNS IP address, enter the following RACADM command:
racadm set iDRAC.IPv4.DNSFromDHCP 0
racadm set iDRAC.IPv4.DNSFromDHCP.DNS1 <primary DNS IP address>
racadm set iDRAC.IPv4.DNSFromDHCP.DNS2 <secondary DNS IP address>
4.
If you want to configure a list of user domains so that you only need to enter the user name when logging in to the web interface, use
the following command:
racadm set iDRAC.UserDomain.<index>.Name <fully qualified domain name or IP Address of the
domain controller>
You can configure up to 40 user domains with index numbers between 1 and 40.
Extended schema Active Directory overview
Using the extended schema solution requires the Active Directory schema extension.
Best practices for extended schema
The extended schema uses Dell association objects to join iDRAC and permission. This allows you to use iDRAC based on the overall
permissions granted. The default Access Control List (ACL) of Dell Association objects allows Self and Domain Administrators to manage
the permissions and scope of iDRAC objects.
By default, the Dell Association objects do not inherit all permissions from the parent Active Directory objects. If you enable inheritance for
the Dell Association object, the inherited permissions for that association object are granted to the selected users and groups. This may
result in unintended privileges being provided to the iDRAC.
To use the Extended Schema securely, Dell recommends not enabling inheritance on Dell Association objects within the extended schema
implementation.
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. The user class is one example of a
class
that is stored in the
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
Configuring user accounts and privileges
131