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

Creating roles that follow organizational structure, Restricting roles

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 129 highlights

For example, an organization might have two types of users: administrators of the iLO 3 device or host server, and users of the iLO 3 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 3 administrators in that role, and the administrative role. Figure 57 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 57 Admin user gaining admin role right, example 1 In Figure 58, 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 58 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 enable 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 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 121) or "Setting time restrictions" (page 122). Directory-enabled remote management 129

  • 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
For example, an organization might have two types of users: administrators of the iLO 3 device
or host server, and users of the iLO 3 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 3 administrators in that role, and the administrative role.
Figure 57
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 57 Admin user gaining admin role right, example 1
In
Figure 58
, 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 58 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 enable
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 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 121)
or
“Setting time restrictions” (page 122)
.
Directory-enabled remote management
129