Try Duo's trusted access solution now.
Free TrialDuo integrates with your Array AG SSL VPN to add two-factor authentication to any VPN login, complete with inline self-service enrollment and Duo Prompt.
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 Array AG SSL VPN users before you begin to deploy Duo.
To integrate Duo with your Array AG SSL VPN, 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!
You also need to download the custom Duo theme for the AG from the Array site. An Array support portal login is required.
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 /opt/duoauthproxy/uninstall
.
After the installation completes, you will need to configure the proxy.
The Duo Authentication Proxy configuration file is named authproxy.cfg, and is 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 |
Linux | /opt/duoauthproxy/conf/authproxy.cfg |
The configuration file is formatted as a simple INI file. Section headings appear as:
[section]
Individual properties beneath a section appear as:
name=value
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.
In this step, you'll set up the Proxy's primary authenticator — the system which will validate users' existing passwords. In most cases, this means configuring the Proxy to communicate with Active Directory or RADIUS.
To use Active Directory/LDAP as your primary authenticator, add an [ad_client]
section to the top of your config file. Add the following properties to the section:
Required
host
|
The hostname or IP address of your domain controller. |
service_account_username
|
The username of a domain account that has permission to bind to your directory and perform searches. We recommend creating a service account that has read-only access. |
service_account_password
|
The password corresponding to |
search_dn
|
The LDAP distinguished name (DN) of an Active Directory container or organizational unit (OU) containing all of the users you wish to permit to log in. For example:
|
Optional
host_2
|
The hostname or IP address of a secondary/fallback domain controller. You can add additional domain controllers as |
security_group_dn
|
To further restrict access, specify the LDAP distinguished name (DN) of a security group that contains the users who should be able to log in. Other users will not pass primary authentication. For example:
|
For example:
[ad_client]
host=1.2.3.4
host_2=1.2.3.5
service_account_username=duoservice
service_account_password=password1
search_dn=DC=example,DC=com
security_group_dn=CN=DuoVPNUsers,OU=Groups,DC=example,DC=com
For advanced Active Directory configuration, see the full Authentication Proxy documentation.
To use RADIUS as your primary authenticator, add a [radius_client]
section to the top of your config file. Then add the following properties to the section:
Required
host
|
The IP address of your RADIUS server. You can add backup servers with |
secret
|
A secret to be shared between the Authentication Proxy and your existing RADIUS server. If you're on Windows and would like to encrypt this secret, see Encrypting Passwords in the full Authentication Proxy documentation. |
Optional
port
|
The authentication port on your RADIUS server. Use Default: |
pass_through_all
|
If this option is set to Default: |
For example:
[radius_client]
host=1.2.3.4
secret=radiusclientsecret
In addition, make sure that the RADIUS server is configured to accept authentication requests from the Authentication Proxy.
For advanced RADIUS configuration, see the full Authentication Proxy documentation.
Next, we'll set up the Authentication Proxy to work with your Array AG SSL VPN. 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 [radius_server_iframe2]
.
Required
type
|
array | ||||||
ikey
|
Your integration key. |
||||||
skey
|
Your secret key. |
||||||
api_host
|
Your API hostname (e.g. "api-XXXXXXXX.duosecurity.com"). |
||||||
radius_ip_1
|
The IP address of your Array AG SSL VPN. |
||||||
radius_secret_1
|
A secret to be shared between the proxy and your Array AG SSL VPN. If you're on Windows and would like to encrypt this secret, see Encrypting Passwords in the full Authentication Proxy documentation. |
||||||
client
|
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. |
Optional
port
|
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. Default: 1812. |
||||
failmode
|
Either "safe" or "secure":
|
||||
radius_ip_2
|
The IP address of your second Array AG SSL VPN, if you have one. You can specify additional devices as as |
||||
radius_secret_2
|
The secrets shared with your second Array AG SSL VPN, if using one. You can specify secrets for additional devices as |
A completed config file, using Active Directory as the primary authenticator, should look something like:
[ad_client]
host=1.2.3.4
service_account_username=duoservice
service_account_password=password1
search_dn=cn=Users,dc=example,dc=com
[radius_server_iframe]
type=array
ikey=DIXXXXXXXXXXXXXXXXXX
skey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
api_host=api-XXXXXXXX.duosecurity.com
radius_ip_1=5.6.7.8
radius_secret_1=radiussecret1
client=ad_client
port=1812
failmode=safe
Make sure to save your configuration file when done.
View video guides for proxy deployment at the Authentication Proxy Overview or see the Authentication Proxy Reference Guide for additional configuration options.
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 in to the Array AG administrative interface. Change the mode from "Enable" to "Config".
Navigate to the Virtual Site that you'd like to protect using the drop-down list in the upper left corner.
Click on AAA under the "Site Configuration" menu on the left.
On the General tab, ensure that the Enable AAA option is checked, then click the Server tab. Once on the Server tab, click on RADIUS.
Enter a Server Name and Description for the new RADIUS server and click the Add button. Your new RADIUS server is added to the list. Double-click it to open the "Advanced RADIUS Server Configuration" page.
On the "Advanced RADIUS Server Configuration" page, click the Add RADIUS Server link in the lower right.
In the Add RADIUS Server form, enter the following information:
Server IP | The IP address of your Duo RADIUS proxy |
Server Port | 1812 (or whichever port specified in the Duo RADIUS proxy configuration) |
Secret Password | The RADIUS secret configured on your Duo RADIUS proxy |
Timeout | 60 |
Redundancy Order | 1 if this is the first RADIUS server |
Retries | 5 |
Accounting Port | Default is 1813 (Accounting is not used so any port is fine) |
Click Save to save the RADIUS server settings. The new Duo RADIUS server is shown in the RADIUS SERVER CONFIGURATION list back on the "Advanced RADIUS Server Configuration" page.
Click on the Method tab then click Add Method on the right. Enter a Method Name and Method Description, then in the "General Authentication Configuration" section choose your Duo RADIUS AAA server from the Authentication drop-down list.
Click Save to save the method configuration. The new method is shown in the list. While still on the Method tab, set the AAA Method for Mobile VPN Clients at the bottom to use the Duo RADIUS authentication method you just created.
Click on Web Access under the "Access Method" on the left, and then click the URL Property tab.
Click the Add URL Property link on the right. Leave the "Mask type" set as Rewrite and enter http://localhost/challenge/ as the "URL". Click the Save link on the right when done.
Click the Save Configuration link in the top right corner of the Array AG administrative interface, when prompted for confirmation click OK.
While still logged in to the Array AG Config session, click on Portal under the "Site Configuration" menu on the left, then click the Themes tab.
Click Import Theme. Click the Choose File button and select the zipped theme file you downloaded earlier from Array's support portal. Enter a name for the theme and click Import.
Double-click your newly created theme to get to the "THEME OBJECTS" page, and while on that page double-click the challenge theme object. This takes you to the "OBJECT RESOURCES" page.
Click the Edit link for the index.html file. Locate both occurances of the string api-xxxxxxxx.duosecurity.com
and replace it with the API host name shown on your Array application's properties page in the Duo Admin Panel.
Click Save in the upper right corner when done. You are returned to the "THEME OBJECTS" page. Click the Back to top link to return to the "Themes" page.
Your new custom theme is in the theme list, but is not the default theme. To make it the default theme, click your custom theme once to select it, then click Activate Theme in the upper right.
Click OK in the activation confirmation pop-up. Your custom theme moves to the top of the list after activation.
Click the Save Configuration link in the top right corner of the Array AG administrative interface, when prompted for confirmation click OK.
To test your Array AG two-factor authentication setup, go to the URL that you defined for your sign-in policy. After you complete primary authentication, the Duo enrollment/login prompt appears.
Need some help? Take a look at the Array AG Frequently Asked Questions (FAQ) page or try searching our Array AG Knowledge Base articles or Community discussions. For further assistance, contact Support.