![background image](/i/tripp-lite/128520/tripp-lite-b094-008-2e-m-f-b096-048-b096-016-b094-008-2e-v-b096-032/h/tripp-lite-b094-008-2e-m-f-b096-048-b096-016-b094-008-2e-v-b096-032-152.png)
152
Chapter 9: Authentication
9.1.5 RADIUS/TACACS user configuration
Users may be added to the local Console Server appliance. If they are not added and they log in via remote AAA, a user will
be added for them. This user will not show up in the configurators unless they are specifically added, at which point they are
transformed into a completely local user. The newly added user must authenticate via the remote AAA server, and will not have
any access if it is down.
If a local user logs in, they may be authenticated/authorized from the remote AAA server, depending on the chosen priority of
the remote AAA. A local user's authorization is the union of local and remote privileges.
Example 1:
User A is locally added, and has access to ports 1 and 2. He is also defined on a remote TACACS server, which says he
has access to ports 3 and 4. The user may log in with either his local or TACACS password, and will have access to ports
1 through 4. If TACACS is down, he will need to use his local password, and will only be able to access ports 1 and 2.
Example 2:
User B is only defined on the TACACS server, which says he has access to ports 5 and 6. When he attempts to log in, a
new user will be created for him, and he will be able to access ports 5 and 6. If the TACACS server is down, he will not
have any access.
Example 3:
User C is defined on a RADIUS server only. He has access to all serial ports and network hosts.
Example 4:
User D is locally defined on an appliance using RADIUS for AAA. Even if the user is also defined on the RADIUS server, he
will only have access to those serial ports and network hosts he has been authorized to use on the appliance.
If a “no local AAA” option is selected, then root will still be authenticated locally.
Remote users may be added to the admin group via either RADIUS or TACACS. Users may have a set of authorizations set
on the remote TACACS server. Users automatically added by RADIUS will have authorization for all resources, whereas those
added locally will still need their authorizations specified.
LDAP has not been modified, and will still need locally defined users.
9.1.6 Group support with remote authentication
All Console Servers allow remote authentication via RADIUS, LDAP and TACACS+. With Firmware V3.2 and later, RADIUS
and LDAP can provide additional restrictions on user access based on group information or membership. For example, with
remote group support, RADIUS and LDAP users can belong to a local group that has been setup to have restricted access to
serial ports, network hosts and managed devices.
Remote authentication with group support works by matching a local group name with a remote group name provided by
the authentication service. If the list of remote group names returned by the authentication service matches any local group
names, the user is given permissions as configured in the local groups.
To enable group support to be used by remote authentication services:
• Select
Serial & Network: Authentication
• Select the relevant
Authentication Method
• Check the
Use Remote Groups
button
9.1.7 Remote groups with RADIUS authentication
• Enter the
RADIUS Authentication and Authorization Server Address
and
Server Password
• Click Apply
• Edit the Radius user’s file to include group information and restart the Radius server
When using RADIUS authentication, group names are provided to the Console Server using the Framed-Filter-Id attribute. This
is a standard RADIUS attribute, and may be used by other devices that authenticate via RADIUS.
To interoperate with other devices using this field, the group names can be added to the end of any existing content in the