Applies To:Show Versions
Configuring Remote TACACS+ Authentication
Overview of remote authentication for application traffic
As an administrator in a large computing environment, you can set up the BIG-IP® system to use this server to authenticate any network traffic passing through the BIG-IP system. This type of traffic passes through a virtual server and through Traffic Management Microkernel (TMM) interfaces. Remote authentication servers typically use one of these protocols:
- Lightweight Directory Access Protocol (LDAP)
- Remote Authentication Dial-in User Service (RADIUS)
- TACACS+ (derived from Terminal Access Controller Access Control System [TACACS])
- Online Status Certificate Protocol (OCSP)
- Certificate Revocation List Distribution Point (CRLDP)
To configure remote authentication for this type of traffic, you must create a configuration object and a profile that correspond to the type of authentication server you are using to store your user accounts. For example, if your remote authentication server is an LDAP server, you create an LDAP configuration object and an LDAP profile. When implementing a RADIUS, SSL OCSP, or CRLDP authentication module, you must also create a third type of object. For RADIUS and CRLDP authentication, this object is referred to as a server object. For SSL OCSP authentication, this object is referred to as an OCSP responder.
To configure remote authentication for this type of traffic, you must create a configuration object and a profile that correspond to the type of authentication server you are using to store your user accounts.
Creating a TACACS+ configuration object
- On the Main tab of the navigation pane, click .
- From the Authentication menu, choose Configurations.
- Click Create.
- In the Name field, type a unique name for the configuration object, such asmy_tacacs_config.
- From the Type list, select TACACS+.
- For the Servers setting, select a server name in the Available list, and using the Move button, move the name to the Selected list.
In the Secret field, type the secret key used to encrypt and decrypt packets sent or received from the server.
Do not use the pound sign ( # ) in the secret for TACACS+ servers.
- In the Confirm Secret field, re-type the secret you specified in the Secret field.
From the Encryption list, select an encryption
Option Description Enabled Choose this option if you want the system to encrypt the TACACS+ packets. Disabled Choose this option if you want the system to send unencrypted TACACS+ packets.
In the Service Name field, type the name of the service
that the user is requesting to be authenticated for use; typically,
Specifying the service makes it possible for the TACACS+ server to behave differently for different types of authentication requests. Examples of service names that you can specify are: ppp, slip, arap, shell, tty-daemon, connection, system, and firewall.
In the Protocol Name field, type the name of the protocol associated with the value specified in the Service Name field.
This value is usually ip. Examples of protocol names that you can specify are: ip, lcp, ipx, stalk, vines, lat, xremote, tn3270, telnet, rlogin, pad, vpdn, ftp, http, deccp, osicp, and unknown.
- Click Finished.
Creating a custom TACACS+ profile
On the Main tab, click
. The Profiles list screen opens.
The New Authentication Profile screen opens.
- In the Name field, type a unique name for the profile.
- Select TACACS+ from the Type list.
- Select tacacs in the Parent Profile list.
- Select the TACACS+ configuration object that you created from the Configuration list.
- Click Finished.
Modifying a virtual server for TACACS+ authentication
On the Main tab, click
.The Virtual Server List screen opens.
- Click the name of a virtual server.
- From the Configuration list, select Advanced.
- For the Authentication Profiles setting, in the Available field, select a custom TACACS+ profile, and using the Move button, move the custom TACACS+ profile to the Selected field.
- Click Update to save the changes.