Cisco ASA 5505 Configuration Manual page 691

Chapter 32 Configuring Management Access
When configuring command authorization with a TACACS+ server, do not save your configuration until
you are sure it works the way you want. If you get locked out because of a mistake, you can usually
recover access by restarting the adaptive security appliance. If you still get locked out, see the
"Recovering from a Lockout" section on page
Be sure that your TACACS+ system is completely stable and reliable. The necessary level of reliability
typically requires that you have a fully redundant TACACS+ server system and fully redundant
connectivity to the adaptive security appliance. For example, in your TACACS+ server pool, include one
server connected to interface 1, and another to interface 2. You can also configure local command
authorization as a fallback method if the TACACS+ server is unavailable. In this case, you need to
configure local users and command privilege levels according to the
Authorization" section on page
This section includes the following topics:
•
•
•
TACACS+ Command Authorization Prerequisites
Complete the following tasks as part of your command authorization configuration:
•
Configuring Commands on the TACACS+ Server
You can configure commands on a Cisco Secure Access Control Server (ACS) TACACS+ server as a
shared profile component, for a group, or for individual users. For third-party TACACS+ servers, see
your server documentation for more information about command authorization support.
See the following guidelines for configuring commands in Cisco Secure ACS Version 3.1; many of these
guidelines also apply to third-party servers:
•
Note
•
•
OL-20339-01
TACACS+ Command Authorization Prerequisites, page 32-19
Configuring Commands on the TACACS+ Server, page 32-19
Enabling TACACS+ Command Authorization, page 32-22
Configure CLI and enable authentication (see the
section on page 32-15).
The adaptive security appliance sends the commands to be authorized as "shell" commands, so
configure the commands on the TACACS+ server as shell commands.
Cisco Secure ACS might include a command type called "pix-shell." Do not use this type for
adaptive security appliance command authorization.
The first word of the command is considered to be the main command. All additional words are
considered to be arguments, which need to be preceded by permit or deny.
For example, to allow the show running-configuration aaa-server command, add show
running-configuration to the command field, and type permit aaa-server in the arguments field.
You can permit all arguments of a command that you do not explicitly deny by checking the Permit
Unmatched Args check box.
For example, you can configure just the show command, and then all the show commands are
allowed. We recommend using this method so that you do not have to anticipate every variant of a
command, including abbreviations and ?, which shows CLI usage (see
32-24.
32-13.
"Configuring Local Command Authorization"
Cisco ASA 5500 Series Configuration Guide using ASDM
Configuring AAA for System Administrators
"Configuring Command
Figure 32-1).
32-19