HP Integrity iLO 2 Operations Guide

For example, an organization might have two types of users: administrators of the iLO 2 device
or host server, and users of the iLO 2 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 2 administrators in that role, and the administrative role.
Figure 67 shows one way that an administrative user gains admin role right. The admin user’s
initial login right is granted through the regular user role. After the initial login, more advanced
rights are assigned to the admin user through the admin role such as server reset and remote
console.
Figure 67 Admin User Gaining Admin Role Right, Example 1
In Figure 68, the admin user gains the admin role right in a different way. The admin user initially
logs in through the admin role and is immediately assigned admin rights (server reset, remote
console, and login).
Figure 68 Admin User Gaining Admin Role Right, Example 2
Creating Roles that Follow Organizational Structure
Often, administrators within an organization are placed into a hierarchy in which subordinate
administrators must assign rights independently of ranking administrators. In this case, it is useful
to have one role that represents the rights assigned by higher-level administrators, and to allow
subordinate administrators to create and manage their own roles.
Restricting Roles
Restrictions enable you to limit the scope of a role. A role only grants rights to those users who
satisfy the role's restrictions. Using restricted roles creates users with dynamic rights that change
based on the time of day or network address of the client.
For step-by-step instructions on how to create network and time restrictions for a role, see “Setting
Role Restrictions” (page 189) or “Setting Time Restrictions” (page 190).
Directory-Enabled Remote Management 197