Protocols And Standards; Aaa Configuration Task List - 3Com 4510G Configuration Manual

13) The HWTACACS client sends the user authorization request packet to the HWTACACS server.
14) The HWTACACS server sends back the authorization response, indicating that the user is
authorized now.
15) Knowing that the user is now authorized, the HWTACACS client pushes the configuration
interface of the NAS to the user.
16) The HWTACACS client sends a start-accounting request to the HWTACACS server.
17) The HWTACACS server sends back an accounting response, indicating that it has received the
start-accounting request.
18) The user logs off.
19) The HWTACACS client sends a stop-accounting request to the HWTACACS server.
20) The HWTACACS server sends back a stop-accounting response, indicating that the
stop-accounting request has been received.

Protocols and Standards

The protocols and standards related to AAA, RADIUS, HWTACACS include:
RFC 2865: Remote Authentication Dial In User Service (RADIUS)
RFC 2866: RADIUS Accounting
RFC 2867: RADIUS Accounting Modifications for Tunnel Protocol Support
RFC 2868: RADIUS Attributes for Tunnel Protocol Support
RFC 2869: RADIUS Extensions
RFC 1492: An Access Control Protocol, Sometimes Called TACACS

AAA Configuration Task List

The basic procedure to configure AAA is as follows:
1) Configure the required AAA schemes.
Local authentication: Configure local users and related attributes, including usernames and
passwords of the users to be authenticated.
Remote authentication: Configure the required RADIUS and/or HWTACACS schemes, and
configure user attributes on the servers accordingly.
2) Configure the AAA methods: Reference the configured AAA schemes in the users' ISP domains.
Authentication method: No authentication (none), local authentication (local), or remote
authentication (scheme)
Authorization method: No authorization (none) , local authorization (local), or remote
authorization (scheme)
Accounting method: No accounting (none), local accounting (local), or remote accounting
(scheme)
For login users, it is necessary to configure the authentication mode for logging into the user interface
as scheme. For detailed information, refer to Login Configuration of the System Volume.
1-10