Two factor authentication for Cisco ASA SSL VPN

 

The LoginTC RADIUS Connector is a complete two-factor authentication virtual machine packaged to run within your corporate network. The LoginTC RADIUS Connector enables Cisco ASA to use LoginTC for the most secure two-factor authentication. For instructions using direct authentication then you may be interested in: Two factor authentication for Cisco ASA SSL VPN Alternative.

User Experience

There are a wide variety of authentication mechanism users can use to perform MFA with Cisco ASA/Firewall/VPN product suite.

• Push Normal
• Software OTP
• Hardware OTP
• SMS OTP
• Cientless

Video Instructions Architecture

Authentication Flow

1. A user attempts access with their existing Cisco AnyConnect client with username / password
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 Cisco ASA
9. User is granted access to Cisco ASA 2 factor authentication

Compatibility

Cisco ASA appliance compatibility:

• Cisco ASA 5505
• Cisco ASA 5506-X Series
• Cisco ASA 5508-X
• Cisco ASA 5510-X
• Cisco ASA 5512-X
• Cisco ASA 5515-X
• Cisco ASA 5516-X
• Cisco ASA 5525-X
• Cisco ASA 5545-X
• Cisco ASA 5555-X
• Cisco ASA 5585-X Series
• Cisco appliance supporting RADIUS authentication

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:
  • 1024 MB RAM
  • 8 GB disk size

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. Unzip the file
3. Import the virtual appliance your computer virtualization software
   • Instructions for Hyper-V
4. Ensure that the LoginTC RADIUS Connector has a virtual network card
5. Start the virtual appliance
6. You will be presented with a console dashboard:
7. The first thing you must do is set the logintc-user password:
8. By default the appliance network is configured by DHCP. If you wish to manually configure the network, use the Down arrow key to navigate to Network Configuration and DNS Configuration
9. For access to the web interface select Web Server and then Start:It may take 5-10 seconds to start the first time:
10. Once started, access the web interface by navigating to the URL mentioned in the information box:

The LoginTC RADIUS Connector runs CentOS 7.7 with SELinux. A firewall runs with the following open ports:

Port	Protocol	Purpose
22	TCP	SSH access
1812	UDP	RADIUS authentication
1813	UDP	RADIUS accounting
8888	TCP	Web interface
443	TCP	Web interface
80	TCP	Web interface
80	TCP	Package updates (outgoing)
123	UDP	NTP, Clock synchronization (outgoing)

Configuration for Cisco ASA MFA

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

1. LoginTC

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. First Factor

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. 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 and Encryption

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 a configuration 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 Configuration

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 configuration file by clicking + Create your first configuration:

LoginTC Settings

Configure which LoginTC Application to us:

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:

First Authentication Factor

Configure the first authentication factor to be used in conjunction with LoginTC. You may use Active Directory / LDAP or an existing RADIUS server. You may also opt not to use a first factor, in which case LoginTC will be the only authentication factor.

Active Directory / LDAP Option

Select Active Directory if you have an AD Server. For all other LDAP-speaking directory services, such as OpenDJ or OpenLDAP, select LDAP:

Configuration values:

Property	Explanation	Examples
host	Host or IP address of the LDAP server	ldap.example.com or 192.168.1.42
port (optional)	Port if LDAP server uses non-standard (i.e., 389/636)	4000
bind_dn	DN of a user with read access to the directory	cn=admin,dc=example,dc=com
bind_password	The password for the above bind_dn account	password
base_dn	The top-level DN that you wish to query from	dc=example,dc=com
attr_username	The attribute containing the user’s username	sAMAccountName or uid
attr_name	The attribute containing the user’s real name	displayName or cn
attr_email	The attribute containing the user’s email address	mail or email
Group Attribute (optional)	Specify an additional user group attribute to be returned the authenticating server.	4000
RADIUS Group Attribute (optional)	Name of RADIUS attribute to send back	Filter-Id
LDAP Group (optional)	The name of the LDAP group to be sent back to the authenticating server.	SSLVPN-Users
encryption (optional)	Encryption mechanism	ssl or startTLS
cacert (optional)	CA certificate file (PEM format)	/opt/logintc/cacert.pem

Click Test to validate the values and then click Next.

Existing RADIUS Server Option

If you want to use your existing RADIUS server, select RADIUS:

Configuration values:

Property	Explanation	Examples
host	Host or IP address of the RADIUS server	radius.example.com or 192.168.1.43
port (optional)	Port if the RADIUS server uses non-standard (i.e., 1812)	1812
secret	The secret shared between the RADIUS server and the LoginTC RADIUS Connector	testing123

Click Test to validate the values and then click Next.

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.

No Passthrough (default)

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

Static 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

Active Directory / LDAP Group

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
LoginTC challenge auth groups	Comma separated list of groups for which users will be challenged with LoginTC	SSLVPN-Users or two-factor-users
host	Host or IP address of the LDAP server	ldap.example.com or 192.168.1.42
port (optional)	Port if LDAP server uses non-standard (i.e., 389/636)	4000
bind_dn	DN of a user with read access to the directory	cn=admin,dc=example,dc=com
bind_password	The password for the above bind_dn account	password
base_dn	The top-level DN that you wish to query from	dc=example,dc=com
attr_username	The attribute containing the user’s username	sAMAccountName or uid
attr_name	The attribute containing the user’s real name	displayName or cn
attr_email	The attribute containing the user’s email address	mail or email
encryption (optional)	Encryption mechanism	ssl or startTLS
cacert (optional)	CA certificate file (PEM format)	/opt/logintc/cacert.pem

Click Test to validate the values and then click Next.

Client and Encryption

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	The IP address of your RADIUS client (e.g. your RADIUS-speaking VPN)	192.168.1.44
secret	The secret shared between the LoginTC RADIUS Connector and its client	bigsecret

Under Authentication Mode select Challenge

The user will be prompted on how they wish to proceed with second-factor authentication (e.g. LoginTC Push, OTP, bypass code). Your RADIUS client must support RADIUS challenges to use this. Challenging the user will often result in a better user experience. 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 and then click the /var/log/logintc/authenticate.log tab to view the log file and troubleshoot:

Cisco ASA SSL VPN Configuration

Once you are satisfied with your setup, configure your Cisco ASA client 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 protect your clientless and AnyConnect VPN setups with LoginTC. The instructions (tailored for Cisco ASA AnyConnect 2.5) can be used for existing setups as well.

1. Launch your Cisco ASA ASDM
2. Click AAA Local Users:
3. Under AAA Server Groups click Add:
   

   Property	Explanation	Example
   Accounting Mode	Indicates how accounting messages are sent. Recommended single mode.	single mode
   Reactivation Mode	Specifies the method by which failed servers are reactivated.	depleted
   Dead Time	Time for which a RADIUS server is skipped over by transaction requests	10
   Max Failed Attempts	Maximum number of retransmission attempts. Recommended 1.	1

4. Select Protocol: RADIUS
5. Click Add
6. Select the newly created group
7. Under Servers in the Selected Group click Add:
   

   Property	Explanation	Example
   Interface Name	Name of protected Cisco interface	inside
   Server name or IP Address	Address of your LoginTC RADIUS Connector	192.168.1.7
   Timeout	Authentication timeout. We recommend 70 seconds if you set the LoginTC Request timeout to 60 seconds.	70
   Server Authentication Port	RADIUS authentication port. Must be 1812.	1812
   Server Accounting Port	RADIUS accounting port. Must be 1813.	1813
   Retry Interval	Length of time between retries	5
   Server Secret Key	The secret shared between the LoginTC RADIUS Connector and its client	bigsecret
   Microsoft CHAPv2 Capable	Whether or not the RADIUS server uses CHAPv2. Must be unchecked

8. Click Clientless SSL VPN Access:
9. Click Connection Profiles:
10. Select DefaultWEBVPNGroup, click Edit:
11. For the AAA Server Group select group made in steps 3-5
12. Click OK

Configure Timeout

By default, the Cisco AnyConnect client will timeout after 12 seconds on Windows and after 30 seconds on Mac OS X. Your users may require more time to authenticate, so the following steps will guide you in creating a profile to override the default timeout.

1. Click on AnyConnect Client Profile
2. Click the Add button
3. Uncheck Auto Reconnect
4. In the sidebar, click on Preferences(Cont) and scroll to the bottom
5. Enter 80 for Authentication Timeout Values (or 10 seconds longer than the AAA RADIUS server timeout and 20 seconds longer than the LoginTC RADIUS Connector Request Timeout)
6. Click OK
7. In the sidebar, click on Server List
8. Click on Add to add a server
9. Enter the FQDN of your Cisco ASA VPN exposed end-point in the Hostname and a hostname or IP Address in the Host AddressClick OK
10. Click Apply
11. Click on Group Policies under Network (Client) Access
12. Click on the group policy that you have assigned to your VPN (e.g. DfltGrpPolicy)
13. Under Advanced > AnyConnect Client Select your profile

To test, navigate to your Cisco ASA clientless VPN portal and attempt access.

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 the LoginTC Admin is performed using User Sync Tool.

Logging

Logs can be found on the Logs tab:

Troubleshooting

User Receives Multiple LoginTC Requests

See the Knowledge Base article for more information: My Cisco ASA AnyConnect SSL VPN users receive multiple LoginTC requests. What can I do?

Time Out After 12 Seconds

Ensure that you have configured the AnyConnect Client Profile. Also ensure that the profile Hostname is the same hostname that your end-users use to connect to the VPN.

Receiving Multiple Requests

Ensure that you have configured the AnyConnect Client Profile. Also ensure that the profile Hostname is the same hostname that your end-users use to connect to the VPN.

See the Knowledge Base article for more information: My Cisco ASA AnyConnect SSL VPN users receive multiple LoginTC requests. What can I do?

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:

Upgrading

From 3.X

Follow these instructions to upgrade your LoginTC RADIUS virtual appliance to the latest version (3.0.7):

1. SSH into the virtual appliance or open the console (use same username / password as web GUI)
2. cd /tmp
3. curl -O https://www.logintc.com/downloads/logintc-radius-connector-3.0.7-upgrade.sh
4. sudo sh logintc-radius-connector-3.0.7-upgrade.sh

The upgrade script will restart your appliance after upgrading.

From 2.X

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

Additional Resources

• Recommended settings for an optimal user experience for VPN access
• Challenge Authentication Mode
• My Cisco ASA AnyConnect SSL VPN users receive multiple LoginTC requests. What can I do?