Overview of Using Cloudpath as TACACS+ Server

You can use your Cloudpath system as a TACACS+ server to manage device access and usage.

Cloudpath Enrollment System is a TACACS+ server which acts as network access control for network devices. TACACS+ provides Authentication, Authorization, and Accounting services for network devices, and specifically provides:

  • Centralized authentication and identity for access management to network devices.
  • Per-command authorization on network devices.
  • Logs for all user-entered commands.
Note: With TACACS+, authentication and authorization are separate processes.
Note: Cloudpath supports TACACS+ in a single-tenant environment only.

A TACACS+ client can be any device with TACACS+ client support, such as RUCKUS ICX switches, RUCKUS Network Controllers, Cisco switches and routers, and others. All traffic is encrypted. The following figure illustrates the basic flow of device-to-Cloudpath TACACS+ server communication.

Flow of Device-to-Cloudpath TACACS+ Server Communication

Note: Port 49 is used for the TCP connection between a network device and the TACACS+ server.

Authentication via TACACS+

The steps for how a user such as a network administrator gets authenticated by the Cloudpath TACACS+ server are:

  1. The user attempts to gain access to the network device by doing one of the following:
    • Logging into the device using Telnet, console, SSH, or a web management interface.
    • Entering the Privileged EXEC level or CONFIG level of the CLI on the device.
  2. The user is prompted for a username and password.
  3. The user enters the correct username and password.
  4. The device sends a request containing the username and password to the TACACS+ server.
  5. The username and password are validated in the TACACS server authentication backend or local user repository.
  6. If both username and password are valid, the user gets authenticated.

Authorization via TACACS+

Two types of TACACS+ authorization are supported:

  • Exec authorization. This type of authorization determines the user-privilege level when the user is authenticated, as follows:
    1. A user logs into the network device using Telnet, console, SSH, or a web management interface.
    2. The user gets authenticated.
    3. The device communicates with the TACACS+ server to determine the privilege level of the user.
    4. The TACACS+ server sends a response back to the device that contains an A-V (Attribute-Value) pair with the privilege level of the user.
    5. The user is granted the specified privilege level.
  • Command authorization. With this type of authorization, the switch communicates with the TACACS+ server to determine whether the user is authorized to run specific commands, as the following process shows:
    1. A Telnet, console, SSH, or web management interface user who has already been authenticated by the TACACS+server enters a command on the network device.
    2. The device looks in its configuration file to determine if the command has a privilege level that requires TACACS+ command authorization.
    3. If the command does have a privilege level that requires authorization, the device consults the TACACS+ server to determine if the user is authorized to run the command.
    4. If the user is authorized to run the command, the command gets executed.

Accounting via TACACS+

The steps for how accounting works on the TACACS+ server are:

  1. One of the following events occur on the switch/smartzone device:A user logs into the management interface using Telnet or SSH :
    • A user enters a command for which accounting has been configured.
    • A system event occurs, such as a reboot or reloading of the configuration file.
    • The device checks the configuration to see if the event is one for which TACACS+ accounting is required.
  2. If the event requires TACACS+ accounting, the device sends a TACACS+ Accounting Start packet to the TACACS+ accounting server, containing information about the event.
  3. The TACACS+ accounting server acknowledges the Accounting Start packet.
  4. The TACACS+ accounting server records information about the event.
  5. When the event is concluded, the device sends an Accounting Stop packet to the TACACS+ accounting server.
  6. The TACACS+ accounting server acknowledges the Accounting Stop packet.