cisco · 10 pp.
Cisco Catalyst 2960: Настройка кэширования авторизации и аутентификации AAA
Related manuals
Contents
Document text
Information About Implementing Authorization and Authentication Profile Caching
Configuring AAA Authorization and Authentication Cache The AAA Authorization and Authentication Cache feature allows you to cache authorization and authentication responses for a configured set of users or service profiles, providing performance improvements and an additional level of network reliability. Users and service profiles that are returned from authorization and authentication responses can be queried from multiple sources and need not depend solely on an offload server.
This feature also provides a failover mechanism so that if a network RADIUS or TACACS+ server is unable to provide authorization and authentication responses network users and administrators can still access the network.
Prerequisites for Implementing Authorization and Authentication Profile Caching, on page 1 Information About Implementing Authorization and Authentication Profile Caching, on page 1 How to Implement Authorization and Authentication Profile Caching, on page 3 Configuration Examples for Implementing Authorization and Authentication Profile Caching, on page 9 Feature History for Implementing Authorization and Authentication Profile Caching, on page 10 PrerequisitesforImplementingAuthorizationandAuthentication Profile Caching The following prerequisites apply to implementing authorization and authentication profile caching:
• Understand how you want to implement profile caching, that is, are profiles being cached to improve network performance or as a failover mechanism if your network authentication and authorization servers (RADIUS and TACACS+) become unavailable. • RADIUS and TACACS+ server groups must already be configured. Information About Implementing Authorization and Authentication Profile Caching The following sections provide information about implementing authorization and authentication profile caching. Configuring AAA Authorization and Authentication Cache 1
Authorization and Authentication Profile Caching as a Failover Mechanism
Network Performance Optimization Using Authorization and Authentication Profile Caching RADIUS and TACACS+ clients run on Cisco devices and send authentication requests to a central RADIUS or TACACS+ server that contains all user authentication and network service access information. The device is required to communicate with an offload RADIUS or TACACS+ server to authenticate a given call and then apply a policy or service to that call. Unlike authentication, authorization, and accounting (AAA) accounting, AAA authentication and authorization is a blocking procedure, which means the call setup may not proceed while the call is being authenticated and authorized.
Thus, the time required to process the call setup is directly impacted by the time required to process such an authentication or authorization request from the device to the offload RADIUS or TACACS+ server, and back again. Any communication problems in the transmission, offload server utilization, and numerous other factors cause significant degradation in a device's call setup performance because of the AAA authentication and authorization step. The problem is further highlighted when multiple AAA authentications and authorizations are needed for a single call or session.
A solution to this problem is to minimize the impact of such authentication requests by caching the authentication and authorization responses for specific users on the device, thereby removing the need to send the requests to an offload server again and again. This profile caching adds significant performance improvements to the call setup times. Profile caching also provides an additional level of network reliability because user and service profiles that are returned from authentication and authorization responses can be queried from multiple sources and need not depend solely on an offload server.
To take advantage of this performance optimization, you need to configure the authentication method list so that the AAA cache profile is queried first when a user attempts to authenticate to the device. See Method Lists in Authorization and Authentication Profile Caching section for more information. Authorization and Authentication Profile Caching as a Failover Mechanism If, for whatever reason, RADIUS or TACACS+ servers are unable to provide authentication and authorization responses, network users and administrators can be locked out of the network. The profile caching feature allows usernames to be authorized without having to complete the authentication phase.
For example, a user by the name user100@example.com with the password secretpassword1 can be stored in a profile cache using the regular expression .*@example.com. Another user by the name user101@example.com with the password secretpassword2 can also be stored using the same regular expression, and so on. Because the number of users in the .*@example.com profile could run into thousands, it is not feasible to authenticate each user with their personal password. Therefore, authentication is disabled, and each user simply accesses authorization profiles from a common Access Response stored in the cache.
The same reasoning applies in cases where higher-end security mechanisms such as Challenge Handshake Authentication Protocol (CHAP), Microsoft Challenge Handshake Authentication Protocol (MS-CHAP), or Extensible Authentication Protocol (EAP), which use an encrypted password between a client and AAA offload server. To allow these unique secure username and password profiles to retrieve their authorization profiles, authentication is bypassed. To take advantage of this failover capability, you need to configure the authentication and authorization method list so that the cache server group is queried last when a user attempts to authenticate to the device.
See Method Lists in Authorization and Authentication Profile Caching section for more information. Configuring AAA Authorization and Authentication Cache Network Performance Optimization Using Authorization and Authentication Profile Caching Configuring AAA Authorization and Authentication Cache 2
How to Implement Authorization and Authentication Profile Caching
Method Lists in Authorization and Authentication Profile Caching A method list is a sequential list describing the authentication methods to be queried in order to authenticate a user. Cisco support methods such as local (use the local Cisco IOS XE database), none (do nothing), RADIUS server group, or TACACS+ server group. Typically, more than one method can be configured into a method list. Cisco IOS XE software uses the first listed method to authenticate users. If that method fails to respond, the Cisco IOS XE software selects the next authentication method listed in the method list.
This process continues until there is successful communication with a listed authentication method, or until all the methods defined in the method list are exhausted. To optimize network performance or provide failover capability using the profile caching feature, change the order of the authentication and authorization methods in the method list. To optimize network performance, make sure the cache server group appears first in the method list. For failover capability, the cache server group should appear last in the method list.
Authorization and Authentication Profile Caching Guidelines Because the number of usernames and profiles that can request to be authenticated or authorized at a given device on a given point of presence (POP) can be quite extensive, it is not feasible to cache all of them. Therefore, only usernames and profiles that are commonly used or that share a common authentication and authorization response should be configured to use caching.
Commonly used usernames such as aolip and aolnet, which are used for America Online (AOL) calls, or preauthentication dialed number identification service (DNIS) numbers used to connect Public Switched Telephone Network (PSTN) calls to a network-attached storage device, along with domain-based service profiles, are all examples of usernames and profiles that can benefit from authentication and authorization caching. General Configuration Procedure for Implementing Authorization and Authentication Profile Caching To implement authorization and authentication profile caching, complete the following procedure: 1.
Create cache profile groups and define the rules for what information is cached in each group. Entries that match based on exact username and regular expressions, or specify all authentication and authorization requests, can be cached. 2. Update existing server groups to reference newly defined cache groups. 3. Update authentication or authorization method lists to use the cached information to optimize network performance or provide a failover mechanism. How to Implement Authorization and Authentication Profile Caching The following sections provide information about the various tasks that comprise authorization and authentication profile-caching configuration.
Configuring AAA Authorization and Authentication Cache Method Lists in Authorization and Authentication Profile Caching Configuring AAA Authorization and Authentication Cache 3
Creating Cache Profile Groups and Defining Caching Rules
Creating Cache Profile Groups and Defining Caching Rules Perform this task to create a cache profile group, define the rules for what information is cached in that group, and verify and manage cache profile entries. Procedure Configuring AAA Authorization and Authentication Cache Creating Cache Profile Groups and Defining Caching Rules Command or Action Purpose Step 1 enable Example: Device> enable Enables privileged EXEC mode. Enter your password, if prompted. Step 2 configure terminal Example: Device# configure terminal Enters global configuration mode. Step 3 aaa new-model Example: Device(config)# aaa new-model Enables the AAA access control model.
Step 4 aaa cache profile group-name Example: Device(config)# aaa cache profile networkusers@companyname Defines an authentication and authorization cache profile server group and enters profile map configuration mode. Step 5 profile name [no-auth] Example: Device(config-profile-map)# profile networkuser1 no-auth Creates an individual authentication and authorization cache profile based on a username match. • The name argument must be an exact match to a username being queried by an authentication or authorization service request. • Use the no-auth keyword to bypass authentication for this user.
Note • For EAP-PEAP with MSCHAPv2 and EAP-PEAP with GTC methods, AAA authentication caching for 802.1x is supported with or without bypass authentication. However, for EAP methods such as EAP-TLS and EAP-MD5, AAA authentication caching for 802.1x is only supported with bypass authentication. Configuring AAA Authorization and Authentication Cache 4