The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Information about AAA
Based on a user ID and password combination, AAA is used to authenticate and authorize users. A key secures communication with AAA servers.
In many circumstances, AAA uses protocols such as RADIUS or TACACS+, to administer its security functions. If your router or access server is acting as a network access server, AAA is the means through which you establish communication between your network access server and your RADIUS or TACACS+, security server.
Although AAA is the primary (and recommended) method for access control, additional features for simple access control are available outside the scope of AAA, such as local username authentication, line password authentication, and enable password authentication. However, these features do not provide the same degree of access control that is possible by using AAA.
Separate AAA configurations are made for the following services:
AAA Service Configuration Option |
Related Command |
---|---|
Telnet or SSH login |
aaa authentication login default |
Console login |
aaa authentication login console |
Authentication provides the method of identifying users, including login and password dialog, challenge and response, messaging support, and, depending on the security protocol that you select, encryption. Authentication is the way a user is identified prior to being allowed access to the network and network services. You configure AAA authentication by defining a named list of authentication methods and then applying that list to various interfaces.
Authentication is accomplished as follows:
Authentication Method |
Description |
---|---|
Local database |
Authenticates the following with a local lookup database of usernames or passwords |
Remote RADIUS or TACACS+ server |
Authenticates the following with a local lookup database of usernames or passwords |
None |
Authenticates the following with only a username. |
Authorization restricts the actions that a user is allowed to perform. It provides the method for remote access control, including one-time authorization or authorization for each service, per-user account list and profile, user group support, and support of IP, IPX, ARA, and Telnet.
Remote security servers, such as RADIUS and TACACS+, authorize users for specific rights by associating attribute-value (AV) pairs, which define those rights, with the appropriate user. AAA authorization works by assembling a set of attributes that describe what the user is authorized to perform. These attributes are compared with the information contained in a database for a given user, and the result is returned to AAA to determine the user’s actual capabilities and restrictions.
Accounting provides the method for collecting and sending security server information used for billing, auditing, and reporting, such as user identities, start and stop times, executed commands (such as PPP), number of packets, and number of bytes. Accounting enables you to track the services that users are accessing, as well as the amount of network resources that they are consuming.
Accounting tracks and maintains a log of every SVS management session. You can use this information to generate reports for troubleshooting and auditing purposes. You can store accounting logs locally or send them to remote AAA servers.
Remote AAA server groups can provide failovers if one remote AAA server fails to respond, which means that if the first server in the group fails, the next server in the group is tried until a server responds. Multiple server groups can provide failovers for each other in this same way.
If all remote server groups fail, the local database is used for authentication.
The Cisco Nexus 1000V does not support usernames that have all numeric characters and does not create local usernames that have all numeric characters. If a username that has all numeric characters already exists on an AAA server and is entered during login, the Cisco Nexus 1000V does authenticate the user.
Parameters |
Default |
---|---|
Console authentication method |
local |
Default authentication method |
local |
Login authentication failure messages |
Disabled |
Configuring AAA
If authentication is to be done with TACACS+ server group(s), you have already added the group(s).
Before beginning this procedure, you must be logged in to the CLI in EXEC mode.
switch# configure terminal switch(config)# aaa authentication login console group tacgroup switch(config)# exit switch# show aaa authentication default: group tacgroup console: group tacgroup switch# copy running-config startup-config switch#
switch# configure terminal switch(config)# aaa authentication login default group tacacs switch(config)# aaa authentication login console group tacacs
Use this procedure to enable the login authentication failure message to display if the remote AAA servers do not respond.
The following is the Login Authentication Failure message:
Remote AAA servers unreachable; local authentication done. Remote AAA servers unreachable; local authentication failed.
Before beginning this procedure, you must be logged in to the CLI in EXEC mode.
Command or Action | Purpose | |
---|---|---|
Step 1 | switch# configure terminal | Places you into global configuration mode. |
Step 2 | switch(config)# aaa authentication login error-enable | Enables login authentication failure messages. The default is disabled |
Step 3 | switch(config)# exit | Exits global configuration mode and returns you to EXEC mode |
Step 4 | switch# show aaa authentication login error-enable | (Optional) Displays the login failure message configuration. |
Step 5 | switch# copy running-config startup-config | (Optional) Copies the running configuration to the startup configuration. |
switch# configure terminal switch(config)# aaa authentication login error-enable switch(config)# exit switch# show aaa authentication login error-enable enabled
Use one of the following commands to verify the configuration:
Command |
Purpose |
---|---|
show aaa authentication [login {error-enable | mschap}] |
Displays AAA authentication information. |
show aaa groups |
Displays the AAA server group configuration. |
show running-config aaa [all] |
Displays the AAA configuration in the running configuration. |
show startup-config aaa |
Displays the AAA configuration in the startup configuration. |
switch# show aaa authentication login error-enable disabled switch#
switch# show running-config aaa all version 4.0(1) aaa authentication login default local aaa accounting default local no aaa authentication login error-enable no aaa authentication login mschap enable no radius-server directed-request no snmp-server enable traps aaa server-state-change no tacacs-server directed-request switch#
switch# show startup-config aaa version 4.0(1)
The following is an AAA configuration example:
aaa authentication login default group tacacs aaa authentication login console group tacacs
This table includes only the updates for those releases that have resulted in additions or changes to the feature.
Feature Name |
Releases |
Feature Information |
---|---|---|
AAA |
Release 5.2(1)IC1(1.1) |
This feature was introduced. |