Two factor authentication for Amazon WorkSpaces

 
Last Updated: December 20, 2024

Overview

The LoginTC RADIUS Connector is a complete two-factor authentication virtual machine packaged to run within your corporate network. The LoginTC RADIUS Connector enables Amazon WorkSpaces to use LoginTC for the most secure two-factor authentication.
 
Explore how LoginTC integrates with Amazon Workspaces below.
 

User Experience

After entering the username and password into the Amazon WorkSpaces form, the user may enter ‘1’ to receive a push notification to their device to approve or enter a valid One-Time Password (OTP) in the same form. This flow works the same for clientless access.

• Push Authentication
• Software OTP
• Hardware OTP
• Bypass Codes

Architecture

Authentication Flow

1. A user attempts access to Amazon WorkSpaces with username / password and MFA in the same form
2. A RADIUS authentication request is sent to the LoginTC RADIUS Connector
3. The username / password is verified against an existing first factor directory (LDAP, Active Directory or RADIUS)
4. An authentication request is made to LoginTC Cloud Services
5. Secure push notification request sent to the user’s mobile or desktop device
6. User response (approval or denial of request) sent to LoginTC Cloud Services
7. The LoginTC RADIUS Connector polls until the user responds or a timeout is reached
8. RADIUS Access-Accept sent back to Amazon WorkSpaces
9. User is granted access to Amazon WorkSpaces

Compatibility

Amazon WorkSpaces compatibility:

• AWS Managed Microsoft AD
• AWS Directory Service or
• AD Connector

Prerequisites

Before proceeding, please ensure you have the following:

• LoginTC Admin Panel account
• Computer virtualization software such as VMware ESXi, VirtualBox, or Hyper-V
• Virtual Machine requirements:
  • 1 vCPU
  • 2 GiB RAM
  • 8 GB disk space

Further assumptions:

• AWS Workspaces and AWS Managed AD for it configured: Launch a WorkSpace using AWS Managed Microsoft AD.
• LoginTC RADIUS Connector appliance installed from AWS Marketplace: Deploy the LoginTC RADIUS Connector in AWS

Create Application

Start by creating a LoginTC Application for your deployment. An Application represents a service (e.g. An application is a service (e.g., VPN or web application) that you want to protect. e) that you want to protect with LoginTC.

Create a LoginTC Application in LoginTC Admin Panel, follow Create Application Steps.

If you have already created a LoginTC Application for your deployment, then you may skip this section and proceed to Installation.

Installation

1. Download the latest LoginTC RADIUS Connector:
   • OVF for ESXi, VirtualBox
   • VHD for Hyper-V
2. Import the virtual appliance your computer virtualization software
   • Instructions for Hyper-V
3. Ensure that LoginTC RADIUS CONNECTOR has a virtual network card
4. Start the virtual appliance
5. You will be with a console prompt:
6. Login using the username logintc-user and default password logintcradius:
7. Once logged in type setup:
8. Follow the on-screen prompt to setup a new password for logintc-user:
9. By default the appliance network is not configured. Manually configure the network by typing 1 and hit enter:
10. Follow the on-screen prompts to setup the network. When done, type 1 and enter to confirm the settings:
11. You will be presented with the network configuration which includes the URL to connect to the appliance from a web browser (example https://172.20.221.105:8443):
12. Navigate to the URL shown in the console dashboard (example: https://172.20.221.105:8443):
13. Login using the username logintc-user and the password that was set in the initial setup:
14. Link to your existing LoginTC organization. The 64-character Organization API Key is found on the LoginTC Admin Panel under Settings >page API >page Click to view, also see Organization API Key:
15. Confirm the LoginTC organization name and click Continue to LoginTC RADIUS Connector:
16. If you have an existing LoginTC RADIUS Connector your wish to import configurations then click Yes, import configurations from an existing LoginTC RADIUS Connector, otherwise click No, continue to the adminsitration panel:

    NOTE
    These instructions assume a new environment. For a complete 2.X / 3.X to 4.X upgrade guide: LoginTC RADIUS Connector Upgrade Guide

17. Now you are ready to use the LoginTC RADIUS Connector:

The LoginTC RADIUS Connector runs a firewall with the following open ports:

Port	Protocol	Purpose
1812	UDP	RADIUS authentication
443	TCP	API traffic
8443	TCP	Web interface

Configuration for Amazon WorkSpaces 2FA

Endpoints describe how the appliance will authenticate your RADIUS-speaking device with an optional first factor and LoginTC as a second factor. Each endpoint has 4 Sections:

1. LoginTC Settings

This section describes how the appliance itself authenticates against LoginTC Admin Panel with your LoginTC Application. Only users that are part of your organization and added to the domain configured will be able to authenticate.

2. User Directory

This section describes how the appliance will conduct an optional first factor. Either against an existing LDAP, Active Directory or RADIUS server. If no first factor is selected, then only LoginTC will be used for authentication.

3. Challenge Strategy / Passthrough

This section describes whether the appliance will perform a LoginTC challenge for an authenticating user. The default is to challenge all users. However with either a static list or Active Directory / LDAP Group you can control whom gets challenged to facilitate seamless testing and rollout.

4. Client Settings

This section describes which RADIUS-speaking device will be connecting to the appliance and whether to encrypt API Key, password and secret parameters.

The web interface makes setting up an endpoint simple and straightforward. Each section has a Test feature, which validates each input value and reports all potential errors. Section specific validation simplifies troubleshooting and gets your infrastructure protected correctly faster.

First Endpoint

Close the console and navigate to your appliance web interface URL. Use username logintc-user and the password you set upon initial launch of the appliance. You will now configure the LoginTC RADIUS Connector.

Create a new endpoint file by clicking + Create your first endpoint:

LoginTC Settings

A list of available Applications will be displayed from your LoginTC organization. Select which LoginTC Application to use:

Configure the application:

Configuration values:

Property	Explanation
Application ID	The 40-character Application ID, retrieve Application ID
Application API Key	The 64-character Application API Key, retrieve Application API Key
Request Timeout	Number of seconds that the RADIUS connector will wait for

The Application ID and Application API Key are found on the LoginTC Admin Panel.

Click Test to validate the values and then click Next:

User Directory

As a result of how AWS implements AD Connector with Multi-factor authentication using an external RADIUS authenticating server the LoginTC RADIUS Connector cannot performing the first factor authentication, rather password verification is performed by the configured directory in AWS. Choose the Continue without a User Directory option and continue.

Challenge Strategy / Passthrough

Configure which users will be challenged with LoginTC. This allows you to control how LoginTC will be phased in for your users. This flexibility allows for seamless testing and roll out.

For example, with smaller or proof of concept deployments select the Static List option. Users on the static list will be challenged with LoginTC, while those not on the list will only be challenged with the configured First Authentication Factor. That means you will be able to test LoginTC without affecting existing users accessing your VPN.

For larger deployments you can elect to use the Active Directory or LDAP Group option. Only users part of a particular LDAP or Active Directory Group will be challenged with LoginTC. As your users are migrating to LoginTC your LDAP and Active Directory group policy will ensure that they will be challenged with LoginTC. Users not part of the group will only be challenged with the configured First Authentication Factor.

Challenge All Users

Select this option if you wish every user to be challenged with LoginTC.

Challenge Users Based on Static Username List

Select this option if you wish to have a static list of users that will be challenged with LoginTC. Good for small number of users.

LoginTC challenge users: a new line separated list of usernames. For example:

            jane.doe
            jane.smith
            john.doe
            john.smith

Challenge Users Based on Group Membership

Select this option if you wish to have only users part of a particular Active Directory or LDAP group to be challenged with LoginTC. Good for medium and large number of users.

Configuration values:

Property	Explanation	Examples
Challenge Groups (Optional)	Comma separated list of groups for which users will be challenged with LoginTC	SSLVPN-Users or two-factor-users
Challenge Groups (Optional)	Comma separated list of groups for which users will always bypass LoginTC	NOMFA-Users

Click Test to validate the values and then click Next.

Client Settings

Configure RADIUS client (e.g. your RADIUS-speaking VPN):

Client configuration values:

Property	Explanation	Examples
name	A unique identifier of your RADIUS client	CorporateVPN
IP Addresss	The IP address of your RADIUS client (e.g. your RADIUS-speaking VPN). Add additional IP Addresses by clicking plus.	192.168.1.44
Shared Secret	The secret shared between the LoginTC RADIUS Connector and its client	bigsecret

Under Authentication Mode select Direct

The LoginTC RADIUS Connector will directly and automatically perform the LoginTC second factor. See User Experience for more information.

Click Test to validate the values and then click Save.

Testing

When you are ready to test your configuration, create a LoginTC user (if you haven’t already done so). The username should match your existing user. Provision a token by following the steps:

1. In a new tab / window log into the LoginTC Admin Panel
2. Click Domains
3. Click on your domain
4. Click on Members
5. Click Issue Token button beside your user:
6. A 10-character alphanumeric activation code will appear beside the user:
7. Open the LoginTC mobile app.
8. Enter the 10-character alphanumeric activation code:
9. Load the token to complete the process

When you have loaded a token for your new user and domain, navigate to your appliance web interface URL:

Click Test Configuration:

Enter a valid username and password; if there is no password leave it blank. A simulated authentication request will be sent to the mobile or desktop device with the user token loaded. Approve the request to continue:

Congratulations! Your appliance can successfully broker first and second factor authentication. The only remaining step is to configure your RADIUS device!

If there was an error during testing, the following will appear:

In this case, click See logs (or click the Logs section):

Amazon WorkSpaces 2FA Configuration

Once you are satisfied with your setup, configure your Amazon WorkSpaces to use the LoginTC RADIUS Connector.

For your reference, the appliance web interface Settings page displays the appliance IP address and RADIUS ports:

The following are quick steps to get access protected with LoginTC. The instructions can be used for existing setups as well.

Configure AWS WorkSpaces

Perform the following steps to integrate MFA to the Managed AD used by an AWS Workspace.
We assume that you have your setup in us-east-1.

1. In the AWS Console go to Directory Service:
2. Select the directory used by the AWS workspace you want to add the MFA to. Click the Directory ID hyperlink to open directory details:
3. Under Networking details, take note down the two IP Addresses of the DNS address of the Managed AD. They will be required configuring the Client Settings of the Endpoint in the LoginTC RADIUS Connector:
4. Scroll down to the Multi-factor authentication section, select Actions, and then select Enable:
5. Complete the required fields:
   

   Property	Explanation	Example
   Display Label	The name of the MFA services	LoginTC RADIUS
   RADIUS server DNS name or IP Addresses	IP Address of the LoginTC RADIUS Connector.	54.159.191.131
   Port	Port used for RADIUS, must be 1812	1812
   Shared secret code	The secret shared between the LoginTC RADIUS Connector and its client	bigsecret
   Confirmed shared secret code	The secret shared between the LoginTC RADIUS Connector and its client	bigsecret
   Protocol	Must be PAP	PAP
   Server timeout (in seconds)	Amount of time in seconds to wait. At least 90s.	90
   Max RADIUS request retries	Amount of times to retry authentication. Must be 1.	1

6. Click Submit
7. You will be taken back to the directory details page. In the Multi-factor authentication section, the RADIUS status will initially be in a Creating state:
   Once the RADIUS status changes to Completed, authentication with the LoginTC RADIUS Connector will be ready:

You are now ready to test your configuration.

Testing (Amazon WorkSpacesConfiguration)

To test use login using MFA, perform the following steps:

• Go to https://clients.amazonworkspaces.com/
• Download the AWS Workspace client based on your operating system
• Install the client and open it
• After entering the registration code, enter your username, password and in the MFA type “1” or the OTP from the app:

User Management

There are several options for managing your users within LoginTC:

• Individual users can be added manually in LoginTC Admin Panel
• Bulk operations using CSV Import
• Programmatically manage user lifecycle with the REST API
• One-way user synchronization of users to LoginTC Admin is performed using User Sync Tool.

Logging

Logs can be found on the Logs tab:

Troubleshooting

No Network Connection

1. First ensure that your LoginTC RADIUS Connector is configured to have a virtual network adapter on eth0
2. Ensure that the virtual network adapter MAC address matches the one in the file /etc/sysconfig/network-scripts/ifcfg-eth0
3. Restart the networking service:

   service network restart

4. If you notice the error that eth0 is not enabled, then check driver messages for more information:

   dmesg | grep eth

5. It’s possible that the virtualization software renamed the network adapter to eth1. If this is the case, rename /etc/sysconfig/network-scripts/ifcfg-eth0 to ifcfg-eth1.

   mv /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth1

   Open the file and update the DEVICE="eth0" line to DEVICE="eth1"

Not Authenticating

If you are unable to authenticate, navigate to your appliance web interface URL and click Status:

Ensure that all the status checks pass. For additional troubleshooting, click Logs:

Unsuccessful authentication may be caused by premature timeouts

Authentication Timing Out

If authentication is failing, it is possible that the authentication requests are timing out too quickly. By default, LoginTC push requests will timeout after 90 seconds. Another timeout value is defined by the RADIUS server configuration. If it is set too low, it will cause requests to prematurely timeout.

Upgrading

From 4.X

The latest LoginTC RADIUS Connector upgrade package can be downloaded here: Download RADIUS Connector (Upgrade)

1. Navigate to SETUP > Upgrade:
2. Click Upload and select your LoginTC RADIUS Connector upgrade file:
3. Click Upload and do not navigate away from the page:
4. Once upload is complete upgrade by clicking Install Now:
5. Wait 10-15 minutes for upgrade to complete:

From 3.X

Complete 3.X to 4.X upgrade guide: LoginTC RADIUS Connector Upgrade Guide

Additional Resources

• Recommended settings for an optimal user experience for VPN access
• Challenge Authentication Mode