HP 2x1Ex16 HP IP Console Viewer User Guide - Page 291

LDAP client behavior overview, UID masks (simple and complex)

Page 291 highlights

LDAP client behavior overview UID masks (simple and complex) The client application login dialog enables you to enter two fields, labeled User name and Password. Before the HP IP Console Viewer was enhanced with support for directory services integration (LDAP), the product supported only one form of authentication, which used an internal database. Therefore, there was no ambiguity about the use of these two fields because the internal database supports only one form of user name. However, Active Directory supports many types of attributes that could sensibly be used as credentials for the purposes of authenticating the user of the client application. After an administrator chooses which Active Directory attributes to use as credentials, the choice is implemented using a feature of the HP IP Console Switch called the UID Mask. This flexibility engenders several questions: • What are the Active Directory attributes that could sensibly be used as credentials? • How does the value of each of those attributes get set in Active Directory? • How is the UID mask in the Manage Console Switch window used to implement a customer's choice of credentials? These questions are addressed in the following subsections. Active Directory attributes that can be used as credentials Several attributes that are candidates for use as credentials are defined when a new user account is initialized in Active Directory. Other candidates are found in the Properties dialog for user objects in Active Directory. In addition, other candidates are available but not readily accessible in the default Properties dialog for user objects. For these attributes, it is necessary to use an Active Directory tool, such as ADSI Editor, to access the attribute and set its value. Attributes initialized during creation of a new user object When a new object is created in Active Directory to represent a user, the dialog presented by Active Directory enables values to be set for the following attribute types: • First Name • Initials • Last Name • Full Name • User Logon Name • User Principal Name NOTE: This attribute is not explicitly labeled in the dialog used to create a new user object. • User Logon Name (pre-Windows® 2000) LDAP client behavior overview 291

  • 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
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339

LDAP client behavior overview
291
LDAP client behavior overview
UID masks (simple and complex)
The client application login dialog enables you to enter two fields, labeled User name and Password.
Before the HP IP Console Viewer was enhanced with support for directory services integration (LDAP), the
product supported only one form of authentication, which used an internal database. Therefore, there was
no ambiguity about the use of these two fields because the internal database supports only one form of
user name. However, Active Directory supports many types of attributes that could sensibly be used as
credentials for the purposes of authenticating the user of the client application. After an administrator
chooses which Active Directory attributes to use as credentials, the choice is implemented using a feature
of the HP IP Console Switch called the UID Mask. This flexibility engenders several questions:
What are the Active Directory attributes that could sensibly be used as credentials?
How does the value of each of those attributes get set in Active Directory?
How is the UID mask in the Manage Console Switch window used to implement a customer's choice
of credentials?
These questions are addressed in the following subsections.
Active Directory attributes that can be used as credentials
Several attributes that are candidates for use as credentials are defined when a new user account is
initialized in Active Directory. Other candidates are found in the Properties dialog for user objects in
Active Directory. In addition, other candidates are available but not readily accessible in the default
Properties dialog for user objects. For these attributes, it is necessary to use an Active Directory tool, such
as ADSI Editor, to access the attribute and set its value.
Attributes initialized during creation of a new user object
When a new object is created in Active Directory to represent a user, the dialog presented by Active
Directory enables values to be set for the following attribute types:
First Name
Initials
Last Name
Full Name
User Logon Name
User Principal Name
NOTE:
This attribute is not explicitly labeled in the dialog used to create a new user object.
User Logon Name (pre-Windows® 2000)