Azure Mfa Integration With Netscaler PDF
Azure Mfa Integration With Netscaler PDF
Deployment Guide
This guide focuses on describing the configuration required for integrating Azure
MFA (Multi-Factor Authentication) with NetScaler.
Citrix.com 1
Azure MFA Integration with NetScaler (LDAP) Deployment Guide
This deployment guide focuses on integrating Microsoft Azure Multi Factor Authentication (MFA) with NetScaler.
This integration will allow use of the Azure MFA server as one of the authentication factors on NetScaler. This
will allow users to use NetScaler for all authentication while being able to utilize Azure's multi factor authentica-
tion capabilities,.
NetScaler is a world-class application delivery controller (ADC) with the proven ability to load balance, acceler-
ate, optimize and secure enterprise applications.
Azure Multi-Factor Authentication seamlessly integrates with NetScaler to provide additional security for logins
and portal access. Multi-factor authentication (MFA) is combined with standard user credentials to increase
security for user identity verification. NetScaler also supports similar capabilties as Azure MFA; this enables
enterprise users to choose how they want their authentication landscape to be built.
In this guide, we will be looking at LDAP based integration for Azure MFA.
The following software versions are used and recommended for this configuration -
Software Version
Configuration Details
The test deployment topology is shown in Figure 1. This features an authentication setup with one NetScaler
appliance, one Azure MFA server and a a backend Active Directory/LDAP server for authentication.
Figure 1: Deployment Topology
1. Now, enable LDAP authentication and add NetScaler as a client. Click the LDAP authentication icon in the
left hand side panel as shown below -
2. When the LDAP Authentication section is opened, select Enable LDAP Authentication.
1. Select the Clients tab and change the port number, if necessary. The default ports are 389 for plaintext and
636 for SSL encryption.
2. if secure LDAP (LDAPS) is in use, click Browse and add the SSL certificate.
1. Click Add in the last dialog box shown to add a new LDAP client.
2. Select the Target tab and verify that it shows LDAP. This completes the adding of NetScaler as an LDAP cli-
ent and enabling of LDAP authentication.
Directory Integration
1. On the Multi-Factor Authentication Server window, click on Directory Integration in the navigation section.
2. When the Directory Integration tool opens, select the Settings tab.
1. Next, configure Company Settings. Click on Company Settings in the Navigation area:
• Text message – select Two-Way and OTP from the dropdown menus:
This completes the configuration for the Company Information Section for LDAP authentication.
Now, as the NetScaler is configured as an LDAP client, access is restricted to the vserver to only MFA users. To
avoid the need for LDAP requests to require MFA, the administrator account has to the configured, and user ac-
counts must be imported from the LDAP directory.
1. Select the user accounts you want to import. Leave the settings as is, in this deployment flow the Import
Phone option is set to Mobile. (Other options are also available)
2. Click the Import button. Then, click OK in the Import Success dialog box.
Now, configure the MFA administrator account to allow LDAP requests without requiring MFA requests.
This guide covers the configuration described above. The SSL certificate and DNS configurations should be in
place prior to setup.
For domain users to be able to log on to the NetScaler appliance by using their corporate email addresses, you
must configure an LDAP authentication server and policy on the appliance and bind it to your VPN VIP address.
(Use of an existing LDAP configuration is also supported)
1. In the NetScaler configuration utility, in the navigation pane, select NetScaler Gateway > Policies > Authen-
tication > LDAP.
2. To create a new LDAP policy: On the Policies tab click Add, and then enter LDAP_Policy as the name. In the
Server field, click the ‘+’ icon to add a new server. The Authentication LDAP Server window appears.
• In the Name field, enter LDAP_Server.
• Select the bullet for Server IP. Enter the IP address of one of your Active Directory domain control-
lers. (You can also point to a virtual server IP for the purpose of redundancy if you are load balancing
domain controllers)
• Specify the port that the NetScaler will use to communicate with the domain controller. Use 389 for
LDAP or 636 for Secure LDAP (LDAPS).
3. Under Connection Settings, enter the base domain name for the domain in which the user accounts reside
within the Active Directory (AD) for which you want to allow authentication. The example below uses
cn=Users,dc=ctxns,dc=net.
4. In the Administrator Bind DN field, add a domain account (using an email address for ease of configuration)
that has rights to browse the AD tree. A service account is advisable, so that there will be no issues with
logins if the account that is configured has a password expiration.
5. Check the box for Bind DN Password and enter the password twice.
6. Under Other Settings: Enter samaccountname as the Server Logon Name Attribute.
7. In the SSO Name Attribute field, enter UserPrincipalName. Enable the User Required and Referrals options.
Leave the other settings as they are.
8. Click on More at the bottom of the screen, then add mail as Attribute 1 in the Attribute Fields section. Leave
Nested Group Extraction in the Disabled state (we are not going to be using this option for this deployment)
An employee trying to log in using is redirected to a NetScaler VPN virtual server that validates the employee's
corporate credentials. This virtual server listens on port 443, which requires an SSL certificate. External and/or
internal DNS resolution of the virtual server's IP address (which is on the NetScaler appliance) is also required.
The following steps require a preexisting virtual server to be in place. In addition, they assume that DNS name
resolution is already in place, and that the SSL certificate is already installed on your NetScaler appliance.
1. In the NetScaler Configuration tab navigate to NetScaler Gateway > Virtual Servers and click the Add but-
ton.
2. In the Gateway Virtual Server window, enter the virtual server's name and IP address.
4. Click Continue.
5. In the Certificates section, select No Server Certificate.
11. Select Bind and from within the Policies window select the LDAP Policy created earlier.
Testing Authentication
Requirements
• A device with the Azure Authenticator mobile application installed. The application can be downloaded from
the platform store for the following devices:
• Windows Phone
• Android
• iOS
• The Azure Users Portal address.
• A computer to access the Users Portal.
• User credentials
Activate Device
1. Log in to the Azure user portal from a browser.
2. On the setup screen, click on Generate Activation Code
Login
Now you are ready to test MFA authentication. Please note the requirements listed below before you start.
General Requirements
• A computer to access the login screen.
• The SSL VPN appliance URL for network sign in.
• User credentials
Phone Call
Required: A phone with the number listed in the AD user account Mobile phone attribute.
1. On a computer, open the login page in a web browser.
2. Enter user credentials.
3. Check the phone for a call.
NOTE: The call originates in the cloud from the Azure MFA application.
Example:
4. Click Verify.
5. The authentication application will communicate with the MFA server to complete authentication.
Conclusion
Citrix NetScaler enables integration with Azure MFA, allowing a multitude of authentication use cases to be deliv-
ered successfully for enterprise customers.
Enterprise Sales
North America | 800-424-8749
Worldwide | +1 408-790-8000
Locations
Corporate Headquarters | 851 Cypress Creek Road Fort Lauderdale, FL 33309 United States
Silicon Valley | 4988 Great America Parkway Santa Clara, CA 95054 United States
Copyright© 2018 Inc. All rights reserved. Citrix, the Citrix logo, and other marks appearing herein are property of
Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered with the U.S. Patent and Trademark
Office and in other countries. All other marks are the property of their respective owner/s.