21-49
Catalyst 6000 Family Software Configuration Guide—Releases 6.3 and 6.4
78-13315-02
Chapter 21 Configuring Switch Access Using AAA
Understanding How Authorization Works
Console> (enable)
set tacacs key tintin_et_milou
The tacacs key has been set to tintin_et_milou.
Console> (enable)
set authentication login tacacs enable telnet
tacacs login authentication set to enable for telnet session.
Console> (enable)
set authentication enable tacacs enable telnet
tacacs enable authentication set to enable for telnet session.
Console> (enable)
set authentication login local disable telnet
local login authentication set to disable for telnet session.
Console> (enable)
set authentication enable local disable telnet
local enable authentication set to disable for telnet session.
Console> (enable)
show tacacs
Tacacs key: tintin_et_milou
Tacacs login attempts: 3
Tacacs timeout: 5 seconds
Tacacs direct request: disabled
Tacacs-Server Status
---------------------------------------- -------
172.20.52.10 primary
Console> (enable)
Understanding How Authorization Works
These sections describe how authorization works:
•
Authorization Overview, page 21-49
•
Authorization Events, page 21-49
•
Primary Options and Fallback Options, page 21-50
•
Command Authorization, page 21-50
•
RADIUS Authorization, page 21-51
Authorization Overview
Catalyst 6000 family switches support and RADIUS authorization. Authorization limits
access to specified users using a dynamically applied access list (or user profile) based on the username
and password pair. The access list resides on the host running the or RADIUS server. The
server responds to the user password information with an access list number that causes the specific list
to be applied.
Authorization Events
You can enable authorization for the following:
•
Commands—When you enable the authorization feature for commands, the user must supply a valid
username and password pair to execute certain commands. You can require authorization for all
commands or for configuration (enable mode) commands only. When a user issues a command, the
authorization server receives the command and user information and compares it against an access
list. If the user is authorized to issue that command, the command is executed; otherwise, the
command is not executed.