Tacacs+ Authentication; Overview - HP ProCurve 2910al Access Security Manual

TACACS+ Authentication

Overview

A3 or
B3
Primary
TACACS+
Server
The switch passes the login
requests from terminals A and B
to the TACACS+ server for
authentication. The TACACS+
server determines whether to
allow access to the switch and
what privilege level to allow for
a given access request.
Figure 4-1. Example of TACACS+ Operation
4-2

Overview

Feature
view the switch's authentication configuration
view the switch's TACACS+ server contact
configuration
configure the switch's authentication methods
configure the switch to contact TACACS+ server(s) disabled
TACACS+ authentication enables you to use a central server to allow or deny
access to the switches covered in this guide (and other TACACS-aware
devices) in your network. This means that you can use a central database to
create multiple unique username/password sets with associated privilege
levels for use by individuals who have reason to access the switch from either
the switch's console port (local access) or Telnet (remote access).
Switch Configured for
A2 or
B2
B4
B1
Access Request
TACACS Server
Response
TACACS+ in the switches covered in this guide manages authentication of
logon attempts through either the Console port or Telnet. TACACS+ uses an
authentication hierarchy consisting of (1) remote passwords assigned in a
TACACS+ server and (2) local passwords configured on the switch. That is,
with TACACS+ configured, the switch first tries to contact a designated
A1
TACACS+ Operation
B
Terminal "B" Remotely Accessing The Switch Via Telnet
Default Menu CLI
n/a — page 4-9
n/a — page 4-
10
disabled — page 4-
11
— page 4-
18
A4
Terminal "A" Directly
A
Accessing the Switch
Via Switch's Console
Port
A1 - A4: Path for Request from
Terminal A (Through Console Port)
B1 - B4: Path for Request from
Terminal B (Through Telnet)
Web
—
—
—
—