5-15
Cisco SCE 8000 10GBE Software Configuration Guide
OL-30621-02
Chapter 5 Configuring the Management Interface and Security
Authentication, Authorization, and Accounting
Authentication, Authorization, and Accounting
•
Information About Authentication, Authorization, and Accounting, page 5-15
•
Configuring the Cisco SCE Platform Client, page 5-19
•
Managing the User Database, page 5-22
•
Configuring AAA Login Authentication, page 5-26
•
Configuring AAA Privilege-Level Authorization Methods, page 5-28
•
Configuring AAA Command-Level Authorization Methods, page 5-28
•
Configuring AAA Accounting, page 5-29
•
•
Information About Authentication, Authorization, and Accounting
•
Login Authentication, page 5-15
•
•
Privilege-Level Authorization, page 5-16
•
General AAA Fallback and Recovery Mechanism, page 5-17
•
is a security application that provides centralized authentication of users attempting to gain
access to a network element. The implementation of protocol allows customers to configure
one or more authentication servers for the Cisco SCE platform, providing a secure means of managing
the Cisco SCE platform, as the authentication server will authenticate each user. This then centralizes
the authentication database, making it easier for the customers to manage the Cisco SCE platform.
services are maintained in a database on a server running, typically, on a UNIX
or Windows NT workstation. You must have access to and must configure a server before the
configured features on your network element are available.
The protocol provides authentication between the network element and the ACS,
and it can also ensure confidentiality, if a key is configured, by encrypting all protocol exchanges
between a network element and a server.
The protocol provides the following three features:
•
Login authentication
•
Privilege level authorization
•
Accounting
Login Authentication
The Cisco SCE platform uses the ASCII authentication message for CLI, Telnet and SSH
access.
allows an arbitrary conversation to be held between the server and the user until the server
receives enough information to authenticate the user. This is usually done by prompting for a username
and password combination.