Chapter 9
Configuring Switch-Based Authentication
Figure 9-2
Remote
PC
RADIUS Operation
When a user attempts to log in and authenticate to a switch that is access controlled by a RADIUS server,
these events occur:
1.
2.
3.
The ACCEPT or REJECT response is bundled with additional data that is used for privileged EXEC or
network authorization. Users must first successfully complete RADIUS authentication before
proceeding to RADIUS authorization, if it is enabled. The additional data included with the ACCEPT or
REJECT packets includes these items:
•
•
RADIUS Change of Authorization
This section provides an overview of the RADIUS interface including available primitives and how they
are used during a Change of Authorization (CoA).
•
•
OL-9775-08
Transitioning from RADIUS to TACACS+ Services
The user is prompted to enter a username and password.
The username and encrypted password are sent over the network to the RADIUS server.
The user receives one of these responses from the RADIUS server:
a.
ACCEPT—The user is authenticated.
REJECT—The user is either not authenticated and is prompted to re-enter the username and
b.
password, or access is denied.
CHALLENGE—A challenge requires additional data from the user.
c.
d.
CHALLENGE PASSWORD—A response requests the user to select a new password.
Telnet, SSH, rlogin, or privileged EXEC services
Connection parameters, including the host or client IP address, access list, and user timeouts
Change-of-Authorization Requests, page 9-20
CoA Request Response Code, page 9-21
R1
RADIUS
server
R2
RADIUS
server
T1
TACACS+
server
T2
TACACS+
server
Workstation
Catalyst 3750-E and 3560-E Switch Software Configuration Guide
Controlling Switch Access with RADIUS
9-19