Using a TACACS+ Server for Authentication

You can use a TACACS+ server for authenticating users. When TACACS+ authentication is enabled, the unit supports Authentication and Authorization as configured on the TACACS+ server. A TACACS+ server can be useful if you want to centrally manage user accounts instead of managing them on each unit individually. The unit can be configured to connect to a second TACACS+ server, allowing for TACACS+ server redundancy.

To configure TACACS+ session parameters

1. Access the page System ▶Session ▶TACACS+.

2. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

TACACS+ Configuration (System ▶Session ▶TACACS+)
General

Server-1 / Server-2

TACACS+ Server Configuration Examples

The following examples are configurations for the TACACS+ server, not for the unit. They apply to a tac_plus server; configuration values may differ for other servers.

Logging in is a two-part process. First, the user is authenticated. Once authenticated, the user may be authorized to gain rights on the system. The server should return AV (attribute-value) pairs for the requested service name.

The first attribute, the privilege level (usually priv-lvl), is evaluated first. This attribute is a numerical value that should be between 0 and 15. On this system, an attribute value of 15 grants Admin rights (All-show, All-Add, All-edit), and all other attribute values grant Viewer rights (All-show). If the specified attribute value is not found, the login attempt is refused because the AV pair was not supplied by the server.

The second attribute, the privilege list (accedian-priv-list), is subsequently evaluated. This attribute is an optional attribute and is ignored if the privilege level is already set to 15 (Admin). The purpose of this attribute is to provide a fine-grained permissions mechanism. The permissions are the same as those that can be configured locally on the unit. The list of tokens is separated by commas. The case-sensitive tokens you indicate can be a mix of locally-defined user permission groups and individual privileges.

Following are configuration examples for the TACACS+ Server using these attributes.

To assign a user to the built-in Admin group
user = tacadmin {
login = cleartext tacadmin
pap = cleartext tacadmin
name = "Test Admin"
# 'shell' service referred to as 'exec'
# in the config
service = exec {
priv-lvl = 15
}
}

To assign a user viewer-only privileges
user = tacviewer {
login = cleartext tacviewer
pap = cleartext tacviewer
name = "Test Tac Viewer"
# 'shell' service referred to as 'exec'
# in the config
service = exec {
priv-lvl = 1
}
}

To assign a user a customized set of privileges and sub-privileges
user = taccfm {
login = cleartext taccfm
pap = cleartext taccfm
name = "Test Tac User CFM"
service = exec {
priv-lvl = 1
accedian-priv-lvl = 7
accedian-priv-list = Config, Config-not rollback
}s
ervice = accedian {
priv-lvl = 1
accedian-priv-list = Config, Config-not-rollback
}
}

If a user is authenticated by TACACS+ but no attributes are specified in the server configuration, the permissions will be set as follows:

• If the username exists locally: Local permissions, as configured on the unit
• If the username does not exist locally: Viewer-only permissions

Managing Access Control Lists

You may use an Access Control List (ACL), which is a network access control mechanism, to prevent or allow specific MAC or IP addresses to access the unit for management purposes.

You can create up to 10 lists and each list can contain up to 40 rules. Each rule allows or blocks addresses. Rules are prioritized using the Priority field, with the rule configured with the highest priority applied first.

It is recommended to set the priorities so the most restrictive rules are performed first. For example, a high-priority rule could grant access to a specific IP address within a subnet, and the next rule could deny access to the whole subnet, thus blocking all remaining IP addresses from that subnet. Another example would be to first deny access to subnet 10.10.10.0/26, then allow access to subnet 10.10.0.0/16.

Once the ACL is created, you can then assign it to one or more interfaces. On each interface you can also select the type of protocol (CLI [SSH and Telnet], WEB, SNMP and NETCONF) to which the ACL applies. Refer to the section Configuring Logical Interfaces on page 22.

Setting Up an ACL

To set up an ACL

1. Access the page System ▶ACL.
   A summary of all lists that have been configured is displayed. For more information on specific parameters, refer to the table at the end of this procedure.

2. Click Add to add a new ACL, or click the Name of an existing ACL to edit its settings.

3. Complete the required fields, then click Apply.

For more information on specific parameters, refer to the following table.

ACL Definition Summary (System ▶ACL)

ACL Definition

Deleting an ACL

To delete an ACL

1. Access the page System ▶ACL.

2. Click the ACL Name to delete.

3. Click Delete.

Viewing ACL Statistics

To view ACL statistics for each interface

1. Access the page System ▶ACL.

2. Click the name of the interface in the Interface List.
   A count of Packets for each ACL rule defined is displayed. The Default Dropped Packets statistic (i.e. associated with the default rule) is displayed at the top of the page.
   For more information on specific parameters, refer to the table "ACL Definition Summary ( System ▶ACL)".

3. To clear the statistics, click the Clear button.

4. To update the statistics, click the Refresh button.