HP ProCurve 9304M Security Manual page 69

21. To configure RADIUS command authorization, select the Management link to display the Management
configuration panel and select the Authorization Methods link to display the Authorization Method panel, as
shown in the following example.
22. Select Commands from the Type field's pulldown menu.
23. Select a privilege level by clicking on one of the following radio buttons:
• 0 – Authorization is performed for commands available at the Super User level (all commands)
• 4 – Authorization is performed for commands available at the Port Configuration level (port-config and
read-only commands)
• 5 – Authorization is performed for commands available at the Read Only level (read-only commands)
NOTE: RADIUS authorization can be performed only for commands entered from Telnet or SSH sessions,
or from the console. No authorization is performed for commands entered at the Web management interface
or SNMP management applications.
NOTE: Since RADIUS authorization relies on the command list supplied by the RADIUS server during
authentication, you cannot perform RADIUS authorization without RADIUS authentication.
24. Click on the radio button next to Radius.
25. Click the Add button to save the change to the device's running-config file.
The authorization method you selected are displayed in the table at the top of the dialog. Each time you add
an authorization method for a given access type, the software assigns a sequence number to the entry.
When authorization is performed, the software tries the authorization sources in ascending sequence order
until the request is either approved or denied. Each time you add an entry for a given access type, the
software increments the sequence number. Thus, if you want to use multiple authentication methods, make
sure you enter the primary authentication method first, the secondary authentication method second, and so
on.
If you need to delete an entry, select the access type and authorization method for the entry, then click Delete.
June 2005
Securing Access to Management Functions
2 - 53