Configuring TACACS+ shell authentication - BlueCat Integrity - 9.3.0

Address Manager Administration Guide

Product name
BlueCat Integrity

The following section describes how to set up TACACS+ authentication service that will be used to log in to Address Manager using SSH.

  • Performing an upgrade to a later version of Address Manager does not remove the TACACS+ configuration file (; however, the configuration for TACACS+ authentication for shell access will be removed and must be configured after the upgrade has been performed.
  • Before you begin, BlueCat strongly recommends creating a "Break Glass" account to ensure that Address Manager can be accessed in case of accidental configuration.
  • You must have an operating TACACS+ server in order to proceed with the steps outlined in this section.
  • SSH users authenticating using TACACS+ will not be running in a restrictive shell environment. If a TACACS+ user must run supported commands, the TACACS+ user must use sudo before the command.

Configuring the initial TACACS+ setup

Run the TACACS+ setup script to configure the TACACS+ server information.

To run the TACACS+ setup script:
  1. Log in to Address Manager using SSH and the root account.
  2. Run the following commands: -h <TACACS server IP address/hostname> \
    -s <TACACS shared secret> \
    -a <TACACS auth service, pap, chap, or login>
    For example: -h -s bcnSharedSecret -a chap

Configuring the TACACS+ groups and users

Once you have configured the TACACS+ server information, you must configure the TACACS+ groups and users to allow them to log in to Address Manager.

To configure TACACS+ groups and users:
  1. Create a user.csv file with the following format:
    username, groupname, sudo commands, paths accessible to the user
    The following is an example of the content and format of the user.csv file:
    user01,group01,"/usr/bin/tail, /usr/local/sbin/rndc, /bin/cat","/var"
    user02,group01,"/usr/bin/ls, /sbin/reboot","/var"
    user03,group02,"/usr/bin/ls, /sbin/reboot"
  2. Create a group.csv file with the following format:
    groupname, sudo commands, path where commands are run
    The following is an example of the content and format of the group.csv file:
    group01,"/sbin/ifup, /sbin/ifdown","/tmp"
    Note: Commands used to grant TACACS+ groups and users are not restricted to the examples presented. You can configure commands as required.
    Attention: BlueCat strongly recommends reviewing the accessible paths and commands that are granted to the TACACS+ groups and users, as they can provide access equivalent to the root user.
  3. Log in to Address Manager using SSH and the root account.
  4. Run the following commands to create the group configuration, followed by the user configuration: group.csv user.csv
    Attention: The same sudo command cannot be used for the user if the command is being used by the group, even if the user belongs to the group. For example, if user01 belongs to group01 and group01 uses sudo run /bin/cat in the group configuration file, user01 cannot use sudo run /bin/cat.

Once you have run the command to configure the users and groups, authorized users and groups can now access SSH using TACACS+ authentication.

Removing the TACACS+ configuration

To remove the TACACS+ configuration:
  1. Create a delete.csv file with the following content:
  2. Log in to Address Manager using SSH and the root account.
  3. Run the following command: delete.csv
  4. Disable TACACS+ service by running the following command: -r

Once you have run the command, the TACACS+ authentication is disabled for SSH connections.