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

Registering iDRAC as a computer in Active Directory root domain, Generating Kerberos keytab file,

Page 144 highlights

Registering iDRAC as a computer in Active Directory root domain To register iDRAC in Active Directory root domain: 1. Click Overview > iDRAC Settings > Network > Network. The Network page is displayed. 2. Provide a valid Preferred/Alternate DNS Server IP address. This value is a valid DNS server IP address that is part of the root domain. 3. Select Register iDRAC on DNS. 4. Provide a valid DNS Domain Name. 5. Verify that network DNS configuration matches with the Active Directory DNS information. For more information about the options, see the iDRAC Online Help. Generating Kerberos keytab file To support the SSO and smart card login authentication, iDRAC supports the configuration to enable itself as a kerberized service on a Windows Kerberos network. The Kerberos configuration on iDRAC involves the same steps as configuring a non-Windows Server Kerberos service as a security principal in Windows Server Active Directory. The ktpass tool (available from Microsoft as part of the server installation CD/DVD) is used to create the Service Principal Name (SPN) bindings to a user account and export the trust information into a MIT-style Kerberos keytab file, which enables a trust relation between an external user or system and the Key Distribution Centre (KDC). The keytab file contains a cryptographic key, which is used to encrypt the information between the server and the KDC. The ktpass tool allows UNIX-based services that support Kerberos authentication to use the interoperability features provided by a Windows Server Kerberos KDC service. For more information on the ktpass utility, see the Microsoft website at: technet.microsoft.com/en-us/library/cc779157(WS.10).aspx Before generating a keytab file, you must create an Active Directory user account for use with the -mapuser option of the ktpass command. Also, you must have the same name as iDRAC DNS name to which you upload the generated keytab file. To generate a keytab file using the ktpass tool: 1. Run the ktpass utility on the domain controller (Active Directory server) where you want to map iDRAC to a user account in Active Directory. 2. Use the following ktpass command to create the Kerberos keytab file: C:\> ktpass.exe -princ HTTP/[email protected] -mapuser DOMAINNAME \username -mapOp set -crypto AES256-SHA1 -ptype KRB5_NT_PRINCIPAL -pass [password] -out c:\krbkeytab The encryption type is AES256-SHA1. The principal type is KRB5_NT_PRINCIPAL. The properties of the user account to which the Service Principal Name is mapped to must have Use AES 256 encryption types for this account property enabled. NOTE: Use lowercase letters for the iDRACname and Service Principal Name. Use uppercase letters for the domain name as shown in the example. 3. Run the following command: C:\>setspn -a HTTP/iDRACname.domainname.com username A keytab file is generated. NOTE: If you find any issues with iDRAC user for which the keytab file is created, create a new user and a new keytab file. If the same keytab file which was initially created is again executed, it does not configure correctly. Creating Active Directory objects and providing privileges Perform the following steps for Active Directory Extended schema based SSO login: 1. Create the device object, privilege object, and association object in the Active Directory server. 2. Set access privileges to the created privilege object. It is recommended not to provide administrator privileges as this could bypass some security checks. 3. Associate the device object and privilege object using the association object. 144 Configuring iDRAC for Single Sign-On or smart card login

  • 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

Registering iDRAC as a computer in Active Directory root
domain
To register iDRAC in Active Directory root domain:
1.
Click
Overview
>
iDRAC Settings
>
Network
>
Network
.
The
Network
page is displayed.
2.
Provide a valid
Preferred/Alternate DNS Server
IP address. This value is a valid DNS server IP address that is part of the root
domain.
3.
Select
Register iDRAC on DNS
.
4.
Provide a valid
DNS Domain Name
.
5.
Verify that network DNS configuration matches with the Active Directory DNS information.
For more information about the options, see the
iDRAC Online Help
.
Generating Kerberos keytab file
To support the SSO and smart card login authentication, iDRAC supports the configuration to enable itself as a kerberized service on a
Windows Kerberos network. The Kerberos configuration on iDRAC involves the same steps as configuring a non–Windows Server
Kerberos service as a security principal in Windows Server Active Directory.
The
ktpass
tool (available from Microsoft as part of the server installation CD/DVD) is used to create the Service Principal Name (SPN)
bindings to a user account and export the trust information into a MIT–style Kerberos
keytab
file, which enables a trust relation between
an external user or system and the Key Distribution Centre (KDC). The keytab file contains a cryptographic key, which is used to encrypt
the information between the server and the KDC. The ktpass tool allows UNIX–based services that support Kerberos authentication to
use the interoperability features provided by a Windows Server Kerberos KDC service. For more information on the
ktpass
utility, see the
Microsoft website at:
technet.microsoft.com/en-us/library/cc779157(WS.10).aspx
Before generating a keytab file, you must create an Active Directory user account for use with the
-mapuser
option of the
ktpass
command. Also, you must have the same name as iDRAC DNS name to which you upload the generated keytab file.
To generate a keytab file using the ktpass tool:
1.
Run the
ktpass
utility on the domain controller (Active Directory server) where you want to map iDRAC to a user account in Active
Directory.
2.
Use the following ktpass command to create the Kerberos keytab file:
C:\> ktpass.exe -princ HTTP/[email protected] -mapuser DOMAINNAME
\username -mapOp set -crypto AES256-SHA1 -ptype KRB5_NT_PRINCIPAL -pass [password] -out
c:\krbkeytab
The encryption type is AES256-SHA1. The principal type is KRB5_NT_PRINCIPAL. The properties of the user account to which the
Service Principal Name is mapped to must have
Use AES 256 encryption types for this account
property enabled.
NOTE:
Use lowercase letters for the iDRACname and Service Principal Name. Use uppercase letters for the domain
name as shown in the example.
3.
Run the following command:
C:\>setspn -a HTTP/iDRACname.domainname.com username
A keytab file is generated.
NOTE:
If you find any issues with iDRAC user for which the keytab file is created, create a new user and a new
keytab file. If the same keytab file which was initially created is again executed, it does not configure correctly.
Creating Active Directory objects and providing privileges
Perform the following steps for Active Directory Extended schema based SSO login:
1.
Create the device object, privilege object, and association object in the Active Directory server.
2.
Set access privileges to the created privilege object. It is recommended not to provide administrator privileges as this could bypass
some security checks.
3.
Associate the device object and privilege object using the association object.
144
Configuring iDRAC for Single Sign-On or smart card login