TACACS protocol
U
SER
G
UIDE
282
TACACS
PROTOCOL
TACACS
PROTOCOL CONFIGURATION
Imola supports Authentication, Accounting and Authorization functions through protocol.
The possible authentication modes are:
local
through user/password database of Imola
remote
through Tacacs protocol
In case of Tacacs authentication is enabled, the remote access is denied if the user types wrong
login and password. In case of no response to Tacacs authentication, local authentication will be
required.
As for configuration of Tacacs authentication mode, the following parameters are the most
important:
the order of authentication: it can be
local
(through internal database) or Tacacs (remote
authentication);
IP address (and port) of Tacacs Server;
The key through which the authentication request (before the authentication of a user) will
be presented to Tacacs Serve;
The use of accounting functions. If they are enabled each command executed will be
notified to the server e memorized by the server on its database;
The use of authorization functions. If they are enabled, before executing a command, it the
authorization is required to the server. Only if the authorization is allowed, the command
will be executed.
After the authentication, the server transmits to the router the level of privilege associated with the
user. Only commands associated with this level can be executed.
In order to configure Tacacs server, the commands are:
set tacacs authhost <IP> [<IP>]
set tacacs authorder tacacs local
set tacacs key <secret-key>
set tacacs retries N
set tacacs timeout N
set tacacs login-timeout N
set tacacs do-accounting
set tacacs do-authorization
set tacacs source <ipaddr>
set tacacs on
The command:
set tacacs authhost <IP> [<IP>]
is used to configure the IP address of the Tacacs Server. Optionally it is possible to specify a further
address to contact when the first one does not reply.
The command: