HP rp3440 HP Integrity and HP 9000 iLO MP Operations Guide, Fifth Edition - Page 119

Using Existing Groups, Using Multiple Roles

Page 119 highlights

Directory-enabled remote management enables you to: • Create iLO MP objects Each device object created represents each device that will use the directory service to authenticate and authorize users. For additional information on creating iLO MP device objects for Active Directory, see "Directory Services" (page 91), "Directory Services for Active Directory" (page 96), and eDirectory "Directory Services for eDirectory" (page 107). In general, you can use the snap-ins provided by HP to create objects. It is useful to give the iLO MP device objects meaningful names, such as the device's network address, DNS name, host server name, or serial number. • Configure iLO MP devices Every iLO MP device that uses the directory service to authenticate and authorize users must be configured with the appropriate directory settings. For details about the specific directory settings, see "Using the LDAP Command to Configure Directory Settings in iLO MP" (page 116). In general, you can configure each device with the appropriate directory server address, iLO MP object distinguished name, and any user contexts. The server address is either the IP address or DNS name of a local directory server, or, for more redundancy, a multihost DNS name. Using Existing Groups Many organizations arrange users and administrators into groups. In many cases, it is convenient to use existing groups and associate these groups with one or more iLO MP role objects. When the devices are associated with the role objects, you can control access to the iLO MP devices associated with the role by adding or deleting members from the groups. When using Microsoft Active Directory, you can place one group within another, or create nested groups. Role objects are considered groups and can include other groups directly. To include other groups directly, add the existing nested group directly to the role and assign the appropriate rights and restrictions. Add new users to either the existing group or to the role. Novell eDirectory does not allow nested groups. In eDirectory, any user who can read a role is considered a member of that role. When adding an existing group, organizational unit, or organization to a role, add the object as a read trustee of the role. All the members of the object are considered members of the role. Add new users to either the existing object or to the role. When you use trustee or directory rights assignments to extend role membership, users must be able to read the iLO MP object representing the iLO MP device. Some environments require the trustees of a role to also be read trustees of the iLO MP object to successfully authenticate users. Using Multiple Roles Most deployments do not require that the same user be in multiple roles managing the same device. However, these configurations are useful for building complex rights relationships. When building multiple-role relationships, users receive all the rights assigned by every applicable role. Roles only grant rights, not revoke them. If one role grants a user a right, the user has the right, even if the user is in another role that does not grant that right. Typically, a directory administrator creates a base role with the minimum number of rights assigned and creates additional roles to add additional rights. These additional rights are added under specific circumstances or to a specific subset of the base role users. For example, an organization might have two types of users: administrators of the iLO MP device or host server, and users of the iLO MP device. In this situation, it makes sense to create two roles, one for the administrators and one for the users. Both roles include some of the same devices, but grant different rights. Sometimes, it is useful to assign generic rights to the lesser role, and include the iLO MP administrators in that role and the administrative role. Directory-Enabled Management 119

  • 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

Directory-enabled remote management enables you to:
Create iLO MP objects
Each device object created represents each device that will use the directory service to
authenticate and authorize users. For additional information on creating iLO MP device
objects for Active Directory, see
“Directory Services” (page 91)
,
“Directory Services for
Active Directory” (page 96)
, and eDirectory
“Directory Services for eDirectory” (page 107)
.
In general, you can use the snap-ins provided by HP to create objects. It is useful to give the
iLO MP device objects meaningful names, such as the device's network address, DNS name,
host server name, or serial number.
Configure iLO MP devices
Every iLO MP device that uses the directory service to authenticate and authorize users
must be configured with the appropriate directory settings. For details about the specific
directory settings, see
“Using the LDAP Command to Configure Directory Settings in iLO
MP” (page 116)
. In general, you can configure each device with the appropriate directory
server address, iLO MP object distinguished name, and any user contexts. The server address
is either the IP address or DNS name of a local directory server, or, for more redundancy,
a multihost DNS name.
Using Existing Groups
Many organizations arrange users and administrators into groups. In many cases, it is convenient
to use existing groups and associate these groups with one or more iLO MP role objects. When
the devices are associated with the role objects, you can control access to the iLO MP devices
associated with the role by adding or deleting members from the groups.
When using Microsoft Active Directory, you can place one group within another, or create nested
groups. Role objects are considered groups and can include other groups directly. To include
other groups directly, add the existing nested group directly to the role and assign the appropriate
rights and restrictions. Add new users to either the existing group or to the role.
Novell eDirectory does not allow nested groups. In eDirectory, any user who can read a role is
considered a member of that role. When adding an existing group, organizational unit, or
organization to a role, add the object as a read trustee of the role. All the members of the object
are considered members of the role. Add new users to either the existing object or to the role.
When you use trustee or directory rights assignments to extend role membership, users must be
able to read the iLO MP object representing the iLO MP device. Some environments require the
trustees of a role to also be read trustees of the iLO MP object to successfully authenticate users.
Using Multiple Roles
Most deployments do not require that the same user be in multiple roles managing the same
device. However, these configurations are useful for building complex rights relationships. When
building multiple-role relationships, users receive all the rights assigned by every applicable
role. Roles only grant rights, not revoke them. If one role grants a user a right, the user has the
right, even if the user is in another role that does not grant that right.
Typically, a directory administrator creates a base role with the minimum number of rights
assigned and creates additional roles to add additional rights. These additional rights are added
under specific circumstances or to a specific subset of the base role users.
For example, an organization might have two types of users: administrators of the iLO MP device
or host server, and users of the iLO MP device. In this situation, it makes sense to create two
roles, one for the administrators and one for the users. Both roles include some of the same
devices, but grant different rights. Sometimes, it is useful to assign generic rights to the lesser
role, and include the iLO MP administrators in that role and the administrative role.
Directory-Enabled Management
119