Duo integrates with your F5 BIG-IP APM to add two-factor authentication to any VPN login, complete with inline self-service enrollment and Duo Prompt. Check out F5 FirePass SSL VPN if you don't have a BIG-IP APM.
The Duo F5 Big-IP configuration with inline enrollment and Duo Prompt supports firmware versions 11.4 and later. Ensure your Big-IP has all current updates for your platform version.
Refer to our alternate instructions if you want to configure Duo on your BIG-IP with automatic push and phone call authentication.
This application communicates with Duo's service on TCP port 443. Firewall configurations that restrict outbound access to Duo's service with rules using destination IP addresses or IP address ranges aren't recommended, since these may change over time to maintain our service's high availability. If your organization requires IP-based rules, please review this Duo KB article.
Before moving on to the deployment steps, it's a good idea to familiarize yourself with Duo administration concepts and features like options for applications, available methods for enrolling Duo users, and Duo policy settings and how to apply them. See all Duo Administrator documentation.
You should already have a working primary authentication configuration for your F5 BIG-IP APM users before you begin to deploy Duo.
To integrate Duo with your F5 BIG-IP APM, you will need to install a local proxy service on a machine within your network. This Duo proxy server also acts as a RADIUS server — there's usually no need to deploy a separate RADIUS server to use Duo.
Next, locate (or set up) a system on which you will install the Duo Authentication Proxy. The proxy supports these operating systems:
Then you'll need to:
The security of your Duo application is tied to the security of your secret key (skey). Secure it as you would any sensitive credential. Don't share it with unauthorized individuals or email it to anyone under any circumstances!
The Duo Authentication Proxy can be installed on a physical or virtual host. We recommend a system with at least 1 CPU, 200 MB disk space, and 4 GB RAM (although 1 GB RAM is usually sufficient).
Ensure that Perl, Python 2.6 or 2.7 (including development headers and libraries), and a compiler toolchain are installed. On most recent RPM-based distributions — like Fedora, RedHat Enterprise, and CentOS — you can install these by running (as root):
$ yum install gcc make python-devel libffi-devel perl zlib-devel
On Debian-derived systems, install these dependencies by running (as root):
$ apt-get install build-essential python-dev libffi-dev perl zlib1g-dev
Download the most recent Authentication Proxy for Unix from https://dl.duosecurity.com/duoauthproxy-latest-src.tgz. Depending on your download method, the actual filename may reflect the version e.g. duoauthproxy-3.2.1-src.tgz. View checksums for Duo downloads here.
Extract the Authentication Proxy files and build it as follows:
$ tar xzf duoauthproxy-latest-src.tgz $ cd duoauthproxy-version-src $ make
Install the authentication proxy (as root):
$ cd duoauthproxy-build $ ./install
Follow the prompts to complete the installation. The installer creates a user to run the proxy service and a group to own the log directory and files. You can accept the default user and group names or enter your own.
If you ever need to uninstall the proxy, run
After the installation completes, you will need to configure the proxy.
The Duo Authentication Proxy configuration file is named authproxy.cfg, and located in the conf subdirectory of the proxy installation. With default installation paths, the proxy configuration file will be located at:
|Platform||Default Configuration Path|
|Windows (64-bit)||C:\Program Files (x86)\Duo Security Authentication Proxy\conf\authproxy.cfg|
|Windows (32-bit)||C:\Program Files\Duo Security Authentication Proxy\conf\authproxy.cfg|
The configuration file is formatted as a simple INI file. Section headings appear as:
Individual properties beneath a section appear as:
The Authentication Proxy may include an existing authproxy.cfg with some example content. For the purposes of these instructions, however, you should delete the existing content and start with a blank text file. We recommend using WordPad or another text editor instead of Notepad when editing the config file on Windows.
At the top of your authproxy.cfg, create a
[duo_only_client] section. This section has no additional parameters to configure.
When using the
[duo_only_client] configuration, the Authentication Proxy will ignore primary credentials and perform Duo factor authentication only.
Next, we'll set up the Authentication Proxy to work with your F5 BIG-IP APM. Create a
[radius_server_iframe] section and add the properties listed below. If you've already set up the Duo Authentication Proxy for a different RADIUS iframe application, append a number to the section header to make it unique, like
Your integration key.
Your secret key.
Your API hostname (e.g. "api-XXXXXXXX.duosecurity.com").
The IP address of your F5 BIG-IP APM.
A secret to be shared between the proxy and your F5 BIG-IP APM. If you're on Windows and would like to encrypt this secret, see Encrypting Passwords in the full Authentication Proxy documentation.
The mechanism that the Authentication Proxy should use to perform primary authentication. This should correspond with a "client" section elsewhere in the config file.
This parameter is optional if you only have one "client" section. If you have multiple, each "server" section should specify which "client" to use.
The port on which to listen for incoming RADIUS Access Requests. If you have multiple RADIUS server sections you should use a unique port for each one.
Either "safe" or "secure":
The IP address of your second F5 BIG-IP APM, if you have one. You can specify additional devices as as
The secrets shared with your second F5 BIG-IP APM, if using one. You can specify secrets for additional devices as
A completed config file, with the Authentication Proxy only performing secondary authentication, should look something like:
[duo_only_client] [radius_server_iframe] type=f5_bigip ikey=DIXXXXXXXXXXXXXXXXXX skey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX api_host=api-XXXXXXXX.duosecurity.com radius_ip_1=188.8.131.52 radius_secret_1=radiussecret1 client=duo_only_client port=1812 failmode=safe
Make sure to save your configuration file when done.
Open an Administrator command prompt and run:
net start DuoAuthProxy
Alternatively, open the Windows Services console (services.msc), locate "Duo Security Authentication Proxy Service" in the list of services, and click the Start Service button.
If the service starts successfully, Authentication Proxy service output is written to the authproxy.log file, which can be found in the log subdirectory.
If you see an error saying that the "service could not be started", open the Application Event Viewer and look for an Error from the source "DuoAuthProxy". The traceback may include a "ConfigError" that can help you find the source of the issue.
Stop and restart the Authentication Proxy service by either clicking the Restart Service button in the Windows Services console or issuing these commands from an Administrator command prompt:
net stop DuoAuthProxy & net start DuoAuthProxy
Open a root shell and run:
# /opt/duoauthproxy/bin/authproxyctl start
To ensure the proxy started successfully, run:
# /opt/duoauthproxy/bin/authproxyctl status
Authentication Proxy service output is written to the authproxy.log file, which can be found in the log subdirectory.
To stop and restart the Authentication Proxy, open a root shell and run:
# /opt/duoauthproxy/bin/authproxyctl restart
If you modify your
authproxy.cfg configuration after initial setup, you'll need to stop and restart the Duo Authentication Proxy service or process for your change to take effect.
Log into the BIG-IP management console and navigate to Access Policy → AAA Servers → RADIUS and click the Create button.
Enter a name for your new Duo RADIUS server. Set the Mode to "Authentication" and fill in the host/port/secret information that corresponds to your Duo Authentication Proxy configuration. Be sure to increase the timeout to 60 seconds.
You'll need to modify an existing Access Policy to use the newly defined Duo RADIUS server for authentication (or create a new one). Navigate to Access Policy → Access Profiles → Access Profiles List and click the Edit... link in the Access Policy column of the profile you want to update to use Duo.
Use the Access Policy editor to insert the Duo RADIUS authentication method after success with your current authentication method (like AD/LDAP). Click the plus symbol in the "Successful" arrow coming off your primary authenticator and type "RADIUS" in the search field on the subsequent page. Select RADIUS Auth and click Add Item.
On the RADIUS Auth properties tab select your Duo RADIUS system in the AAA Server drop-down and cick Save.
Your policy now shows two authenticators (your original method followed by RADIUS).
In this example, Duo RADIUS authentication has been added to an existing Access Policy after successful primary AD authentication.
Click Close to exit the Access Policy editor and return to the Access Profile List page. The profile you just modified may have a yellow status flag. Click the checkbox next to that policy to select it and then click Apply Access Policy. The status flag will turn green.
Consult the BIG-IP Access Policy Manager Configuration Guide for more information about creating and modifying Access Policies or contact F5 support.
Navigate to Access Policy → Customization → Advanced and change the "Edit Mode" to Advanced. Navigate through the Access Profiles tree to the Common folder beneath your Access Policy.
Add the Duo script, using the instructions for your BIG-IP firmware version:
While still in Access Policy Advanced Customization Editor, navigate through the Access Profiles tree to Access Policy > Logon Pages > Logon Page folder beneath your Access Policy.
Click the logon.inc item and locate the
<head> section of the page in the Advanced Customization Editor (around line 90):
Add this line to the
<head> section after the first
meta http-equiv line and click Save:
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
Save the customization changes and return to the Access Profile List page. The profile you just modified may have a yellow status flag. Click the checkbox next to that policy to select it and then click Apply Access Policy. The status flag will turn green.
To test your setup, go to the URL you normally use to log in to your F5 BIG-IP APM in a browser window. After you complete primary authentication, the Duo Prompt or enrollment page appears.
The BIG-IP Edge Client also supports authentication with the Duo Prompt.
Need some help? Take a look at the F5 BIG-IP Frequently Asked Questions (FAQ) page or try searching our F5 BIG-IP Knowledge Base articles or Community discussions. For further assistance, contact Support.