HP 6125XLG R2306-HP 6125XLG Blade Switch Fundamentals Configuration Guide - Page 51

Assigning user roles

Page 51 highlights

User role name level-n (n = 0 to 15) security-audit Permissions • level-0-Has access to the commands of ping, quit, ssh2, super, system-view, telnet, and tracert. Level-0 access rights are configurable. • level-1-Has access to the display commands (except display history-command all) of all features and resources in the system, in addition to all access rights of the user role level-0. Level-1 access rights are configurable. • level-2 to level-8, and level-10 to level-14-Have no access rights by default. Access rights are configurable. • level-9-Has access to all features and resources except RBAC (debugging commands excluded), local users, file management, device management, and the display history-command all command. Level-9 access rights are configurable. • level-15-Has the same access rights as the role network-admin. Security log manager. The user role has access to security log files: • It has access to the commands for displaying and maintaining security log files, for example, the dir, display security-logfile summary, and more commands. • It has access to the commands for managing security log files and security log file system, for example, the info-center security-logfile directory, mkdir, and security-logfile save commands. For more information about security log management, see Network Management and Monitoring. For more information about file system management, see "Managing the file system." IMPORTANT: Only the security-audit user role has access to security log files. Other user roles do not have the access right even if you have configured the user roles to have the access permission. Assigning user roles You assign access rights to users by assigning at least one user role. The users can use the collection of commands and resources accessible to any user role assigned to them. For example, user role A denies access to the qos apply policy command and permits access to only interface Ten-GigabitEthernet 1/1/5, and user role B permits access to the qos apply policy command and all interfaces. With these two user roles, you can access any interface to use the qos apply policy command. Depending on the authentication method, user role assignment has the following methods: • AAA authorization-If scheme authentication is used, the AAA module handles user role assignment. { If the user passes local authorization, the device assigns the user roles specified in the local user account. { If the user passes remote authorization, the remote AAA server assigns the user roles specified on the server to the user. The AAA server can be a RADIUS or HWTACACS server. • None-AAA authorization-If the user uses password authentication or no authentication, the device assigns user roles specified on the user interface. This method also applies to SSH clients that use publickey or password-publickey authentication. User roles assigned to these SSH clients are specified in their respective local device management user accounts. 44

  • 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

44
User role name
Permissions
level-
n
(
n
= 0 to 15)
level-0
—Has access to the commands of
ping
,
quit
,
ssh2
,
super
,
system-view
,
telnet
, and
tracert
. Level-0 access rights are configurable.
level-1
—Has access to the
display
commands (except
display
history-command all
) of all features and resources in the system, in addition
to all access rights of the user role level-0. Level-1 access rights are
configurable.
level-2 to level-8, and level-10 to level-14
—Have no access rights by default.
Access rights are configurable.
level-9
—Has access to all features and resources except RBAC (debugging
commands excluded), local users, file management, device management,
and the
display history-command all
command. Level-9 access rights are
configurable.
level-15
—Has the same access rights as the role network-admin.
security-audit
Security log manager. The user role has access to security log files:
It has access to the commands for displaying and maintaining security log
files, for example, the
dir
,
display security-logfile summary
, and
more
commands.
It has access to the commands for managing security log files and security log
file system, for example, the
info-center security-logfile directory
,
mkdir
, and
security-logfile save
commands.
For more information about security log management, see
Network
Management and Monitoring
. For more information about file system
management, see "
Managing the file system
."
IMPORTANT:
Only the security-audit user role has access to security log files. Other user roles
do not have the access right even if you have configured the user roles to have
the access permission.
Assigning user roles
You assign access rights to users by assigning at least one user role. The users can use the collection of
commands and resources accessible to any user role assigned to them. For example, user role A denies
access to the
qos apply policy
command and permits access to only interface Ten-GigabitEthernet
1/1/5, and user role B permits access to the
qos apply policy
command and all interfaces. With these
two user roles, you can access any interface to use the
qos apply policy
command.
Depending on the authentication method, user role assignment has the following methods:
AAA authorization
—If scheme authentication is used, the AAA module handles user role
assignment.
{
If the user passes local authorization, the device assigns the user roles specified in the local user
account.
{
If the user passes remote authorization, the remote AAA server assigns the user roles specified
on the server to the user. The AAA server can be a RADIUS or HWTACACS server.
None-AAA authorization
—If the user uses password authentication or no authentication, the device
assigns user roles specified on the user interface. This method also applies to SSH clients that use
publickey or password-publickey authentication. User roles assigned to these SSH clients are
specified in their respective local device management user accounts.