TACACS+ and RADIUS Control

This appendix describes using TACACS+ and RADIUS servers to control administrative access to the Analytics Node. It includes the following topics.

Using AAA Services with Arista Analytics
Adding a TACACS+ Server
Setting up a TACACS+ Server
Using RADIUS for Managing Access

Using AAA Services with Arista Analytics

Select remote Authentication, Authorization, and Accounting (AAA) services using TACACS+ or RADIUS servers to control administrative access to the Analytics Node CLI.

The following table lists the accepted Attribute-Value (AV) pairs:


Attributes	Values
BSN-User-Role	admin read-only

A remotely authenticated admin user has full administrative privileges. Authenticate the read-only users on the switch remotely. Read-only access is not conﬁgurable for locally authenticated user accounts.

read-only users can only access login mode, from which they can view most show commands, with some limitations, including the following:

TACACS, SNMP, and user conﬁguration are not visible to the read-only user in the output from the show running-conﬁg command.
show snmp, show user, and show support commands are disabled for the read-only user.
Note: Local authentication and authorization take precedence over remote authentication and authorization.

Privileges at the remote TACACS+ server must be conﬁgured using the following attribute-value pairs:

Supported attribute name: BSN-User-Role
Supported attribute values: admin, read-only

Select a TACACS+ server to maintain administrative access control instead of using the Analytics Node local database. However, it is a best practice to keep the local database as the secondary authentication and authorization method in case the remote server becomes unavailable.

Adding a TACACS+ Server

To view the current TACACS+ conﬁguration, enter the show running-config command, as in the following example:

analytics -1(config)# show run switch BMF-DELIVERY-SWITCH-1 tacacs override-enabled
tacacs server host 1.1.1.1 key 7 020700560208
tacacs server key 7 020700560208 
analytics -1(config)#

It displays the TACACS+ key value as a type7 secret instead of plaintext.

Complete the following steps to conﬁgure the Analytics Node with TACACS+ to control administrative access to the switch.

Identify the IP address of the TACACS+ server and any key required for access using the tacacs server command, which has the following syntax:

tacacs server <server> [key {<plaintext-key> | 0 <plaintext-key> | 7 <encrypted-key>}

You can enable up to four AAA servers by repeating this command for each server. For example, using a plaintext key, the following command enables TACACS+ with the server running at 10.2.3.4.

analytics -1(config-switch)# tacacs server 10.1.1.1 key 0 secret

In case of a missing key, it uses an empty key.

Note: Do not use the pound character (#) in the TACACS secret. It is the start of a comment in the PAM conﬁg ﬁle.

Each TACACS+ server connection can be encrypted using a pre-shared key.

To specify a key for a speciﬁc host, use one of the following commands:

analytics -1# tacacs server host <ip-address> key <plaintextkey> 
analytics -1# tacacs server host <ip-address> key 0 <plaintextkey> 
analytics -1# tacacs server host <ip-address> key 7 <plaintextkey>

Replace plaintextkey with a password up to 63 characters in length. This key can be speciﬁed either globally or for each host. The ﬁrst two forms accept a plaintext (literal) key, and the last form accepts a pseudo-encrypted key, such as that displayed with show running-config.

It uses the global key value when no key is speciﬁed for a given host. An empty key is assumed when no key is speciﬁed globally or speciﬁed for a given host.

The following example uses the key 7 option followed by the encrypted string:

analytics-1(config-switch)# tacacs server 10.1.1.1 key 7 0832494d1b1c11

Note: Be careful while conﬁguring TACACS+ to avoid disabling access to the Analytics Node.

Setting up a TACACS+ Server

Refer to your AAA server documentation for further details or instructions on setting up other servers.

After installing the TACACS+ server, complete the following steps to set up authentication and authorization for Analytics Node with the TACACS+ server:

Conﬁgure users and groups.
In the /etc/tacacs/tac_plus.conf ﬁle, specify the user credentials and group association.
```
# user details
user = user1 {
member = anet-vsa-admin
login = des a9qtD2JXeK0Sk
}
```

Configure the groups to use one of the AV pairs supported by the Analytics Node (for example, BSN-User-Role=admin for admin users).

# group details# 
ANET admin group
group = anet-vsa-admin {
    service = exec {
    BSN-User-Role="admin"
    }
}
# BSN read-only group
group = anet-vsa-read-only {
    service = exec {
    BSN-User-Role="read-only"
    }
}

Configure the TACACS+ server and AAA on the Analytics Node.

tacacs server host <IP address> key server’s secret>
aaa authentication login default group tacacs+ local
aaa authorization exec default group tacacs+ local
aaa accounting exec default start-stop locals group tacacs+

This conﬁguration sets authentication and authorization to ﬁrst connect to the TACACS+ server to verify user credentials and privileges. It checks the user account locally only when the remote server is unreachable. In this example, accounting stores audit logs locally and sends them to the remote server.

Credentials for the Analytics Node and Other Devices

To use the same user credentials for the Analytics Node and other devices, a specific setting in the tac_plus.conf file is necessary. Configure the BSN-User-Role attribute within the tac_plus.conf file as "Optional".

This configuration allows the system to correctly authenticate and authorize users across different types of network devices. The following is an example of the implementation setting in tac_plus.conf.

group = group-admin {
    default service = permit
    service = exec {
        optional BSN-User-Role = "admin"
    }
}

Using RADIUS for Managing Access

RADIUS does not separate authentication and authorization. Be careful when authorizing a user account with a remote RADIUS server to use the password conﬁgured for the user on the remote server.

By default, authentication and authorization functions are set to local while the accounting function is disabled. The only supported privilege levels are as follows:

admin: Administrator access, including all CLI modes and debug options.
read-only: Login access, including most show commands.

Note: You cannot authenticate the admin and recovery user accounts remotely using TACACS. Always authenticate these accounts locally to prevent administrative access from being lost in case a remote AAA server is unavailable.

The admin group provides complete access to all network resources, while the read-only group provides read-only access to all network resources.

DANZ Monitoring Fabric also supports communication with a remote AAA server (TACACS+ or RADIUS). The following summarizes the options available for each function:

Accounting: local, local and remote, or remote.
Authentication: local, local then remote, remote then local, or remote.
Authorization: local, local then remote, remote then local, or remote.
Note: Fallback to local authentication occurs only when the remote server is unavailable, not when authentication fails.

Privileges at the remote TACACS+ server must be conﬁgured using the attribute-value pairs shown in the following table:


Supported attribute names	Supported attribute values
BSN-User-Role	admin read-only

The BSN-AV-Pair attribute sends CLI command activity accounting to the RADIUS server.

Adding a RADIUS Server

Use the following command to specify the remote RADIUS server:

radius server host <server-address> [timeout {<timeout>}][key {{<plaintext>} | 0 {<plaintext>} | 7 {<secret>}}]

For example, the following command identiﬁes the RADIUS server at the IP address 192.168.17.101:

analytics-1(config)# radius server host 192.168.17.101 key admin

You can enter this command up to ﬁve times to specify multiple RADIUS servers. The Analytics Node tries to connect to each server in the order they are conﬁgured.

Setting up a FreeRADIUS Server

After installing the FreeRADIUS server, complete the following steps to set up authentication and authorization for the Analytics Node with the RADIUS server:

Create the BSN dictionary and add it to the list of used dictionaries.

create dictionary /usr/share/freeradius/dictionary.bigswitch with the contents below:
VENDOR      Big-Switch-Networks 37538
BEGIN-VENDOR Big-Switch-Networks
ATTRIBUTE   BSN-User-Role   1         string
ATTRIBUTE   BSN-AVPair      2
            string
END-VENDOR Big-Switch-Networks

Include the bigswitch dictionary in the RADIUS dictionary ﬁle: /usr/share/freeradius/dictionary
```
$INCLUDE     dictionary.bigswitch
```
Conﬁgure a sample user with admin and read-only privileges.
The following is an example that deﬁnes and conﬁgures a user, opens the user ﬁle /etc/freeradius/users, and inserts the following entries:
```
"user1"     Cleartext-Password := "passwd"
            BSN-User-Role := "read-only",
```
Note: It shows the VSA's association with the user and its privileges. A database and an encrypted password are necessary for an actual deployment.
The following example authorizes the user2 for RBAC group AD1:
```
"user2"     Cleartext-Password := "passwd"
            BSN-User-Role := "AD1",
```
Conﬁgure the RADIUS server and AAA on the Analytics Node.
```
radius server host <IP address> key server’s secret>
aaa authentication login default group radius local
aaa authorization exec default group radius local
aaa accounting exec default start-stop group radius local
```
This conﬁguration sets authentication and authorization to ﬁrst connect to the RADIUS server to verify user credentials and privileges. AAA fallback to local occurs only when the remote server is unreachable. In this example, accounting stores audit logs locally and sends them to the remote server.
Add the Analytics Node subnet to the allowed subnets (clients.conf) on the RADIUS server.
It is required when access to the RADIUS server is limited to allowed clients or subnets. The following is an example of the clients.conf ﬁle:
```
client anet {
    ipaddr = 10.0.0.0/8
    secret = <server’s secret>
}
```
Restart the FreeRADIUS service on the server to enable the conﬁguration.
The following is an example accounting record sent from the Analytics Node to the RADIUS server after adding the BSN-AVPair attribute to the /usr/share/freeradius/dictionary.bigswitch ﬁle.
```
s
```

Analytics User Guide