HP Integrity rx2800 HP Integrity iLO 3 Operations Guide - Page 54

LDAP: LDAP group administration, Instead of logging in

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

distinguished name of the group and privileges to be granted to users who are members of that group. ◦ Disable: Deactivates directory support on iLO 3. • Local User Accounts: Includes or excludes access to local iLO 3 user accounts. If local user accounts are enabled, you can log in to iLO 3 using locally stored user credentials. If they are disabled, access is limited to valid directory credentials only. 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 3 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 3. 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 3. All objects listed in the directory can be identified using the unique distinguished name. However, distinguished names can be long, users might not know the 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 the full distinguished name at login. The iLO 3 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 ] LDAP -? See also: LOGIN, UC LDAP: LDAP group administration The LDAP command 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. 54 Using iLO 3

  • 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
distinguished name of the group and privileges to be granted to users who are members
of that group.
◦
Disable: Deactivates directory support on iLO 3.
•
Local User Accounts: Includes or excludes access to local iLO 3 user accounts. If local user
accounts are enabled, you can log in to iLO 3 using locally stored user credentials. If they
are disabled, access is limited to valid directory credentials only.
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 3 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 3.
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 3. All objects listed in the directory can
be identified using the unique distinguished name. However, distinguished names can be
long, users might not know the 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 the full distinguished name at login. The iLO 3 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 ]
LDAP -?
See also:
LOGIN, UC
LDAP
: LDAP group administration
The
LDAP
command 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.
54
Using iLO 3