14.04.2014 Views

Cisco IOS Software Configuration Guide for Cisco Aironet Access ...

Cisco IOS Software Configuration Guide for Cisco Aironet Access ...

Cisco IOS Software Configuration Guide for Cisco Aironet Access ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 13<br />

Configuring RADIUS and TACACS+ Servers<br />

Configuring and Enabling TACACS+<br />

TACACS+ Operation<br />

When an administrator attempts a simple ASCII login by authenticating to an access point using<br />

TACACS+, this process occurs:<br />

1. When the connection is established, the access point contacts the TACACS+ daemon to obtain a<br />

username prompt, which is then displayed to the administrator. The administrator enters a username,<br />

and the access point then contacts the TACACS+ daemon to obtain a password prompt. The access<br />

point displays the password prompt to the administrator, the administrator enters a password, and<br />

the password is then sent to the TACACS+ daemon.<br />

TACACS+ allows a conversation to be held between the daemon and the administrator until the<br />

daemon receives enough in<strong>for</strong>mation to authenticate the administrator. The daemon prompts <strong>for</strong> a<br />

username and password combination, but can include other items, such as the user’s mother’s<br />

maiden name.<br />

2. The access point eventually receives one of these responses from the TACACS+ daemon:<br />

– ACCEPT—The administrator is authenticated and service can begin. If the access point is<br />

configured to require authorization, authorization begins at this time.<br />

– REJECT—The administrator is not authenticated. The administrator can be denied access or is<br />

prompted to retry the login sequence, depending on the TACACS+ daemon.<br />

– ERROR—An error occurred at some time during authentication with the daemon or in the<br />

network connection between the daemon and the access point. If an ERROR response is<br />

received, the access point typically tries to use an alternative method <strong>for</strong> authenticating the<br />

administrator.<br />

– CONTINUE—The administrator is prompted <strong>for</strong> additional authentication in<strong>for</strong>mation.<br />

After authentication, the administrator undergoes an additional authorization phase if authorization<br />

has been enabled on the access point. Administrators must first successfully complete TACACS+<br />

authentication be<strong>for</strong>e proceeding to TACACS+ authorization.<br />

3. If TACACS+ authorization is required, the TACACS+ daemon is again contacted, and it returns an<br />

ACCEPT or REJECT authorization response. If an ACCEPT response is returned, the response<br />

contains data in the <strong>for</strong>m of attributes that direct the EXEC or NETWORK session <strong>for</strong> that<br />

administrator, determining the services that the administrator can access:<br />

– Telnet, rlogin, or privileged EXEC services<br />

– Connection parameters, including the host or client IP address, access list, and administrator<br />

timeouts<br />

Configuring TACACS+<br />

This section describes how to configure your access point to support TACACS+. At a minimum, you<br />

must identify the host or hosts maintaining the TACACS+ daemon and define the method lists <strong>for</strong><br />

TACACS+ authentication. You can optionally define method lists <strong>for</strong> TACACS+ authorization and<br />

accounting. A method list defines the sequence and methods to be used to authenticate, to authorize, or<br />

to keep accounts on an administrator. You can use method lists to designate one or more security<br />

protocols to be used, thus ensuring a backup system if the initial method fails. The software uses the first<br />

method listed to authenticate, to authorize, or to keep accounts on administrators; if that method does<br />

not respond, the software selects the next method in the list. This process continues until there is<br />

successful communication with a listed method or the method list is exhausted.<br />

OL-8191-01<br />

<strong>Cisco</strong> <strong>IOS</strong> <strong>Software</strong> <strong>Configuration</strong> <strong>Guide</strong> <strong>for</strong> <strong>Cisco</strong> <strong>Aironet</strong> <strong>Access</strong> Points<br />

13-23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!