Duo integrates with Amazon WorkSpaces to add two-factor authentication to WorkSpaces client logins.
To protect Amazon WorkSpaces logins with Duo you must be using an AD Connector type directory. The AWS Simple AD directory type does not support multifactor authentication.
View your directory in the WorkSpaces Management Console to obtain the Directory IP addresses. You will need them to configure the Duo Authentication Proxy.
You'll also need to enroll your WorkSpaces users in Duo before they can use multifactor authentication.
This integration communicates with Duo's service on TCP port 443. Also, we do not recommend locking down your firewall to individual IP addresses, since these may change over time to maintain our service's high availability.
To integrate Duo with Amazon WorkSpaces, you will need to install a Duo RADIUS authentication proxy service on one or more EC2 instances in an AWS VPC, or on one or more machines in an on-premise environment. Before proceeding, you should locate (or set up) a system on which you will install the Duo Authentication Proxy. The proxy supports Windows and Linux systems (in particular, we recommend Windows Server 2012 R2 or later, Red Hat Enterprise Linux 6, CentOS 6, Debian 6, or Amazon Linux 2015.03 or later).
It is highly recommended that you assign a fixed private IP to your Authentication Proxy machine, as the WorkSpaces MFA configuration contacts the RADIUS server by IP address.
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 OpenSSL, 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 openssl-devel python-devel libffi-devel
On Debian-derived systems, install these dependencies by running (as root):
$ apt-get install build-essential libssl-dev python-dev libffi-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-2.10.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.
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, you need to set up the Authentication Proxy to work with your AWS WorkSpaces Directory. To do so, create a radius_server_duo_only section with the following properties:
||Your integration key.|
||Your secret key.|
||Your API hostname (api-XXXXXXXX.duosecurity.com).|
||The IP address of your first AWS WorkSpaces Directory Controller.|
||A secret to be shared between the proxy and your AWS WorkSpaces Directory. If you're on Windows and would like to encrypt this secret, see Encrypting Passwords in the full Authentication Proxy documentation.|
||The IP address of your second AWS WorkSpaces Directory Controller.|
A secret to be shared between the proxy and your AWS WorkSpaces Directory. This secret should be the same as was used for
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. Default: 1812.|
Either "safe" or "secure":
A completed config file for AWS WorkSpaces using radius_server_duo_only with no primary authenticator should look something like:
[duo_only_client] [radius_server_duo_only] ikey=DIXXXXXXXXXXXXXXXXXX skey=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX api_host=api-XXXXXXXX.duosecurity.com failmode=safe radius_ip_1=10.20.10.10 radius_secret_1=theradiussecret radius_ip_2=10.20.11.10 radius_secret_2=theradiussecret port=1812
Make sure to save your configuration file when done.
Open an Administrator command prompt and run:
net start DuoAuthProxy
Alternatvely, 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.
Ensure that your WorkSpaces directory controllers are able to access your Authentication Proxy server on UDP port 1812 (or whichever port used in the Authentication Proxy configuration). You may need to add custom incoming and outgoing UDP/1812 rules to your VPC Security Groups to allow access. You can either use the security groups from the directory controllers as the source (as shown here), or use the IP addresses defined for the directory in the WorkSpaces console.
Check the Enable Multi-Factor Authentication option and enter the following information:
|RADIUS server IP address(es)||Enter the IP address(es) of each Duo Authentication Proxy server (comma-separated).|
|Port||Enter 1812 (or whichever port configured on your Duo Authentication Proxy).|
|Shared secret code||Enter the RADIUS secret shared with your Duo Authentication Proxy.|
|Server timeout (in seconds)||Increase the timeout to 20 seconds.|
|Max retries||Leave at the default setting.|
Click Update and Exit to save the RADIUS server profile. The RADIUS status for the directory will change to Completed.
You can deploy two or more Duo Authentication Proxy servers for use with WorkSpaces MFA to provide a highly-available MFA solution. For example, you can install the Duo proxy service on two instances in different Availability Zones (AZ) and then configure WorkSpaces MFA RADIUS settings to use both of those proxy machines. That way if the first server does not respond WorkSpaces MFA will send the authentication request to the next listed RADIUS IP address.
Repeat the Authentication Proxy installation steps on a second Linux or Windows machine instance. The proxy configuration should be identical to the first one (including the RADIUS secret). Start the Duo Authentication Proxy on the second machine.
In the WorkSpaces Directory MFA configuration, enter the RADIUS server information as shown in the previous section but enter the IP addresses of all your Authentication Proxy machines as a comma-separated list in the "RADIUS server IP address(es)" field.
Launch the WorkSpaces client and enter your primary authentication credentials.
You'll be prompted for additional credentials.
Enter a passcode generated by the Duo Mobile app or a hardware token, or type in the name of an out-of-band factor. You may choose from the following factor names:
Perform Duo Push authentication
You can use Duo Push if you've installed Duo Mobile and activated it for this account.
|phone||Perform phone callback authentication.|
Send a new batch of SMS passcodes
Your authentication attempt will be denied. You can then try authenticating again with one of the newly-delivered passcodes.
You can also specify a number after the factor name if you have more than one device enrolled. So you can enter phone2 or push2 if you have two phones enrolled.