HP Integrity BL870c HP Integrity iLO 2 Operations Guide, Eleventh Edition - Page 100

LDAP: LDAP group administration, enables

Page 100 highlights

NOTE: Locally stored user accounts can be active while directory support is enabled. This enables both local- and directory-based user access. If both directory authentication and local user accounts are enabled, login is attempted using the directory first, then using local accounts. • Directory Server IP Address: IP address or host name of the directory server. • Directory Server LDAP Port: Port number for the secure LDAP service on the server. The default value for this port is 636. • Distinguished Name: Specifies where this iLO 2 instance is listed in the directory tree. For example: cn=MP Server,ou=Management Devices,o=hp • User Search Contexts (1,2,3): User name contexts that are applied to the login name entered to access iLO 2. User name contexts are used to locate an object in the tree structure of the directory server and applied to the login name entered to access iLO 2. All objects listed in the directory can be identified using their unique distinguished name. However, distinguished names can be long, users might not know their distinguished names, or they might have accounts in different directory contexts. Search contexts enables users to specify common directory contexts, so that they do not have to enter their full distinguished name at login. iLO 2 attempts to authenticate a user in the directory first by the login name entered, and then by applying user search contexts to that login name until login succeeds. For example: Instead of logging in as cn=user,ou=engineering,o=hp, search context of ou=engineering,o=hp enables a user to log in as user When extended schema is selected and Active Directory is used as a directory server. Microsoft Active Directory has an alternate user credential format. A user can log in as: [email protected], in which case a search context of @domain.hp.com enables the user to login as user. Command line usage and scripting: LDAP [ -directory [ -ldap ] [ -mp ] [ -ip ] [ -port ] [ -dn ] [ -1context ] [ -2context ] [ -3context ] | -groups [ -change [ -dn ] [ rights ] ] [ -list ]] | -nc ] -? See also: LOGIN, US LDAP: LDAP group administration LDAP enters one or more directory groups by specifying the distinguished name of the group and privileges to be granted to users who are members of that group. You must configure group administration information when the directory is enabled with the default schema. The group administration section of the LDAP command enables users to enter one or more directory groups by specifying the distinguished name of the group and privileges to be granted to users who are members of that group. When a user attempts to log in to iLO 2, iLO 2 reads that user's directory name in the directory to determine which groups the user is a member of. iLO 2 compares this information with a list of configured groups. The rights of all the matched groups are combined and assigned to that user. 100 Using iLO 2

  • 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

NOTE:
Locally stored user accounts can be active while directory support is enabled. This
enables both local- and directory-based user access. If both directory authentication and
local user accounts are enabled, login is attempted using the directory first, then using local
accounts.
Directory Server IP Address: IP address or host name of the directory server.
Directory Server LDAP Port: Port number for the secure LDAP service on the server. The
default value for this port is 636.
Distinguished Name: Specifies where this iLO 2 instance is listed in the directory tree. For
example:
cn=MP Server,ou=Management Devices,o=hp
User Search Contexts (1,2,3): User name contexts that are applied to the login name entered
to access iLO 2.
User name contexts are used to locate an object in the tree structure of the directory server
and applied to the login name entered to access iLO 2. All objects listed in the directory can
be identified using their unique distinguished name. However, distinguished names can be
long, users might not know their distinguished names, or they might have accounts in
different directory contexts. Search contexts enables users to specify common directory
contexts, so that they do not have to enter their full distinguished name at login. iLO 2
attempts to authenticate a user in the directory first by the login name entered, and then by
applying user search contexts to that login name until login succeeds. For example:
Instead of logging in as
cn=user,ou=engineering,o=hp
, search context of
ou=engineering,o=hp
enables a user to log in as
user
When extended schema is selected and Active Directory is used as a directory server.
Microsoft Active Directory has an alternate user credential format. A user can log in as:
, in which case a search context of
@domain.hp.com
enables the
user to login as
user
.
Command line usage and scripting
:
LDAP [ -directory [ -ldap <d|x|s> ] [ -mp <e|d>]
[ -ip <hostname/ipaddr> ] [ -port <n>]
[ -dn <text> ] [ -1context <test>]
[ -2context <text>] [ -3context <text>]
| -groups
[ -change <groupNo.> [ -dn <text>]
[ rights <e|d>]
<console|mp|power|user|virtual|all|none> ]
[ -list <groupNo.> ]]
| -nc ]
-?
See also:
LOGIN, US
LDAP
: LDAP group administration
LDAP
enters one or more directory groups by specifying the distinguished name of the group
and privileges to be granted to users who are members of that group.
You must configure group administration information when the directory is enabled with the
default schema.
The group administration section of the LDAP command enables users to enter one or more
directory groups by specifying the distinguished name of the group and privileges to be granted
to users who are members of that group.
When a user attempts to log in to iLO 2, iLO 2 reads that user’s directory name in the directory
to determine which groups the user is a member of. iLO 2 compares this information with a list
of configured groups. The rights of all the matched groups are combined and assigned to that
user.
100
Using iLO 2