Direct LDAP connectivity to Duo for Pulse Connect Secure SSL VPN will reach end of life on March 30, 2024. Customers may not create new Juniper SSL VPN (used with Pulse VPN) applications after September 7, 2023.
We recommend you deploy Duo Single Sign-On for Ivanti Connect Secure to protect Pulse Connect Secure SSL VPN with Duo Single Sign-On, our cloud-hosted identity provider featuring Duo Central and the Duo Universal Prompt.
Another alternative to direct LDAPS connections is adding Duo authentication to Pulse Connect Secure SSL VPN using RADIUS and the Duo Authentication Proxy, for example, RADIUS with Automatic Push for Pulse Connect Secure SSL VPN. See the "Related" links to the left to explore more RADIUS configurations.
Please visit the article Guide to end of life for the Duo LDAP cloud service (LDAPS) used to provide 2FA for Cisco ASA, Juniper Networks Secure Access, and Pulse Secure Connect Secure SSL VPN for further details, and review the Duo End of Sale, Last Date of Support, and End of Life Policy.
These instructions remain available for reconfiguring your existing application.
This Pulse Connect Secure SSL VPN configuration supports inline self-service enrollment and the Duo Prompt for web-based VPN logins, and push, phone call, or passcode authentication for Pulse desktop and mobile client connections that use SSL encryption.
Your device makes a direct connection to Duo's cloud service using LDAPS. LDAPS authentications do not report a client IP address when the Pulse VPN client is used. There is no configurable fail mode for LDAPS connections, so if your device cannot contact Duo's service your users won't be able to log in with Duo.
This integration expressly supports Juniper/Pulse SSL VPN and is not guaranteed to work with any other VPN solution (including Ivanti-branded Pulse system software).
The Pulse/Ivanti Connect Secure RADIUS configuration does not feature the interactive Duo Prompt for web-based logins, but that configuration does capture client IP information for use with Duo policies, such as geolocation and authorized networks, and offers configurable fail mode. This also supports integrating Duo into a single Pulse sign-in URL with multiple authentication realms.
If you are still running Juniper v8.2 or lower firmware, please see the Juniper SSL VPN instructions.
This application communicates with Duo's service on SSL TCP port 636.
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 Duo Knowledge Base article 1337.
Effective June 30, 2023, Duo no longer supports TLS 1.0 or 1.1 connections or insecure TLS/SSL cipher suites. See Duo Knowledge Base article 7546 for additional guidance.
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.
Make sure that Duo is compatible with your Pulse Secure Access SSL VPN. Log on to your Pulse administrator interface and verify that your firmware is version 8.3, 9.0, or later.
You should also have a working primary authentication configuration for your SSL VPN users, e.g. LDAP authentication to Active Directory.
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!
Log on to your Pulse Connect Secure SSL VPN administrator web interface.
Navigate to Authentication → Signing In → Sign-in Pages, click Upload Custom Pages..., and fill in the form:
| Field | Value |
|---|---|
| Name | Duo |
| Page type | Access |
| Templates file | Upload the Duo Juniper package zip file downloaded from the Duo Admin Panel earlier. Your file name will differ from the example image below, reflecting the actual version of the Duo Juniper/Pulse package and your organization's Duo Account ID (visible on the Settings tab of the Duo Admin Panel) as the accountid i.e. Duo-Juniper-8.x-v5-1234-5678-90.zip.You must use the Duo package customized for your account. Uploading the Duo package for the wrong account can cause authentication failures. |
Do not select the "Use Custom Page for Pulse Desktop Client Logon" or "Prompt the secondary credentials on the second page" options, if present.
Check the Skip validation checks during upload box. If you don't you'll see some warnings after uploading the file, which you can ignore.
Click Upload Custom Pages. You may ignore any warnings.
Duo's cloud service currently secures SSL traffic with certificates issued by DigiCert. You'll need to install the DigiCert CA certificates on your SSL VPN so that it can establish the secure LDAP connection to Duo using certificate validation.
To install the DigiCert intermediate CA certificates used by Duo's service:
If you did not already do so, download the DigiCert SHA2 High Assurance Server CA and DigiCert TLS RSA SHA256 2020 CA1 certificates from the DigiCert site for installation on your SSL VPN device.
Navigate to System → Configuration → Certificates → Trusted Server CAs in the Pulse Secure SSL VPN administrative interface.
Click Import Trusted Server CA... then click the Browse button on the "Import Trusted Server CA" page.
Select the DigiCert SHA2 High Assurance Server CA file you downloaded from DigiCert (DigiCertSHA2HighAssuranceServerCA.crt) and click Import Certificate.
After successful import of the DigiCert CA certificate, click Done.
Repeat steps 3 through 5 for the DigiCert TLS RSA SHA256 2020 CA1 (DigiCertTLSRSASHA2562020CA1-1.crt) certificate.
With all necessary CA certificates uploaded to your device, proceed to adding the Duo LDAP server.
Navigate to Authentication → Auth. Servers.
Select LDAP Server from the Auth Server Type list, click New Server, and fill out the form:
| Field | Value |
|---|---|
| Name | Duo-LDAP |
| LDAP Server | Your API hostname (i.e. api-XXXXXXXX.duosecurity.com) |
| LDAP Port | 636 |
| LDAP Server Type | Generic |
| Connection | LDAPS |
| Validate Server Certificate | Check this box |
In the "Authentication required?" section, check the Authentication required to search LDAP box and fill in the form (replacing INTEGRATION_KEY and SECRET_KEY with your application-specific keys).
| Field | Value |
|---|---|
| Admin DN | dc=INTEGRATION_KEY,dc=duosecurity,dc=com |
| Password | SECRET_KEY |
In the "Finding user entries" section:
| Field | Value |
|---|---|
| Base DN | dc=INTEGRATION_KEY,dc=duosecurity,dc=com |
| Filter | cn=<USER> |
Click Save Changes. (After you click Save you might receive a message indicating that the LDAP server is unreachable. You can disregard this message.)
To configure a user realm for the Duo LDAP server, you can do one or more of the following:
If you create a new realm as part of deploying Duo, be sure to create role mapping rules to add users to the new realm.
To add 2FA to a user realm:
Navigate to Users → User Realms and click the link for the user realm to which you want to add secondary authentication (in our example we're using a realm named "Duo-Users").
While on the user realm's "General" tab, expand the "Additional Authentication Server" section, select the Enable additional authentication server check box, and fill out the form:
| Field | Value |
|---|---|
| Authentication #2 | Duo-LDAP |
| Username is | predefined as <USERNAME> |
| Password is | specified by user on sign-in page |
Check the End session if authentication against this server fails box.
Click Save Changes.
Click the Authentication Policy tab at the top of the page and then click Password.
In the "Options for additional authentication server" section, select Allow all users.
Click Save Changes.
To finish setting up your integration, configure a sign-in policy for secondary authentication. In this example we'll use the default */ URL policy, but you can set up a new sign-in policy at a custom URL (like */Duo-testing/) for testing.
Navigate to Authentication → Signing In → Sign-in Policies tab.
Click the link for the sign-in policy that you want to modify.
Select the Duo from the Sign-in page list.
In the "Authentication realm" section, choose User picks from a list of authentication realms....
Choose the user realm you configured earlier, and click Add to move it to the Selected realms box on the right. Make sure this is the only selected realm for this sign-in page.
Click Save Changes.
To test your Pulse Connect Secure 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.
If you're using the Pulse VPN client, you’ll see a "Secondary Password" field when using the Pulse Connect client.
Enter a Duo factor option as the second password. Choose from:
| push |
Perform Duo Push authentication You can use Duo Push if you've installed and activated Duo Mobile on your device. |
| phone | Perform phone callback authentication. |
| sms |
Send a new batch of SMS passcodes. Your authentication attempt will be denied. You can then authenticate with one of the newly-delivered passcodes. |
| A numeric passcode | Log in using a passcode, either generated with Duo Mobile, sent via SMS, generated by your hardware token, or provided by an administrator. Examples: "123456" or "2345678" |
If you plan to permit use of WebAuthn authentication methods (security keys, U2F tokens, or Touch ID) in the traditional Duo Prompt, Duo recommends configuring allowed hostnames for this application and any others that show the inline Duo Prompt before onboarding your end-users.
The Duo Universal Prompt has built-in protection from unauthorized domains so this setting does not apply.
Need some help? Take a look at the Pulse Connect Secure Frequently Asked Questions (FAQ) page or try searching our Pulse Connect Secure Knowledge Base articles or Community discussions. For further assistance, contact Support.
