Supported authentication
methodsThis technical integration guide describes how to integrate a Pulse Secure and Identity as a Service. Although this document specifically covers the Pulse Secure KVM appliance (PA VM), the information provided applies to all Pulse Secure VM Series appliances using the Device Manager software. The aim of this integration is to provide strong, second-factor authentication for your Pulse Secure VM Series appliance solution using Identity as a Service.
Before you begin, review the following:
Supported authentication
methods| Authentication method | Notes | Supported protocols |
| Token | Identity as a Service supports response-only tokens. One-step or two-step authentication (including token push authentication). Note: Challenge/response tokens unsupported with MSCHAPv2. |
EAP-GTC or EAP MSCHAPv2 |
OTP (One Time Password) by SMS or Token |
Two-step authentication only | EAP-GTC |
Note: The Pulse Secure-VM supports only PAP authentication methods with RADIUS.
PrerequisitesComplete the following steps before integrating your authentication system with Identity as a Service:
1. Install and configure your first-factor authentication resource using the documentation provided by the vendor. The first-factor authentication resource can be a RADIUS server or an external authentication resource (a Local DB, LDAP-compliant directory or Windows domain controller through Kerberos).
2. Install and configure the RADIUS appliance using the documentation provided by the vendor. The device must be able to route traffic before integrating with Identity as a Service.
3. Install and configure Identity as a Service and an Identity as a Service Gateway (containing a RADIUS proxy agent). Take note of the shared secrets, IP addresses, and ports you use. You need this information to configure the RADIUS appliance and first-factor authentication resource.
4. If you want to configure your RADIUS appliance and first-factor authentication resource to recognize Identity as a Service user groups, you must define the Identity as a Service user groups first.
The following procedures describe how to configure the Pulse Secure VM Series appliance to use. This integration assumes that you are familiar with the administration interface of the Pulse Secure VM Series appliance. All examples use the Pulse Secure interface.
To set up the Pulse Secure VM Series appliance, you must add the Identity as a Service AAA Server proxy as an AAA (Authentication Authorization Accounting) client, and then configure an SSL connection profile.
Complete the following to integrate Pulse Secure with IDaaS.
Step 1.1: Configure
IDaaS as an AAA Client1. Login to the Pulse Secure Web management. The Pulse Secure main page appears displaying the Dashboard.
Note: It is assumed that you have already deployed and pre-configured the network interface and SSL certificates to Pulse Secure VM software.
2. Expand the Authentication option and select Auth Servers. The Authentication Server page appears.
3. In the New drop-down list, select RADIUS Server, and click New Server. The New RADIUS Server page appears.
4. In the New RADIUS Server page, do the following:
a. In the Name field, enter the Entrust IdentityGuard Radius Server name; for example, Entrust IdentityGuard.
b. In the RADIUS Server field, enter the IP address of the RADIUS server.
c. In the Authentication Port field, enter the port number. The default port is 1812.
d. In the Accounting Port field, enter the port number. The default port is 1813.
e. In the Shared Secret field, enter the RADIUS secret.
f. In the Retries field, enter the number of retries to allow.
g. Leave the other settings at the default values.
5. Scroll down to Custom Radius Rules.
6. Click New Radius Rule. The Add Custom Radius Rule page appears.
7. In the Add Custom radius Rule page, do the following:
a. In the Name field, enter the name for the Radius rule, for example, Radius_Rule.
b. From the Response Packet Type drop-down list, select Access Challenge.
c. From the Radius Attribute drop-down list, select Reply-Message(18).
d. From the Operand drop-down list select matches the expression.
e. In the Value field, enter (.*).
f. Select show Generic Login page.
g. Click Save Changes. You are returned to the Auth Servers page.
Step 1.2: Configure
LDAP as an AAA client1. In the Pulse Connect Secure menu, expand the Authentication option and select Auth Servers. The Authentication Server page appears.
2. From the New drop-down list, select LDAP Server, and click New Server. The LDAP Server Profile page appears.
3. In the New LDAP Server page, do the following:
a. In the Name field, enter the name of your LDAP Server hostname (for example, Ldap).
b. In the LDAP Server field, enter the IP address or host name of the Active Directory.
c. In the Port field, enter 389.
d. From the LDAP Server Type drop-down list, select Active Directory.
e. Click Test Connection to make sure that Pulse Secure can communicate with the LDAP server.
4. In the Authentication Required? pane, do the following:
a. Select the Authentication required to search LDAP check box.
b. In the Admin DN field, enter the domain name (for example, if your Active Directory has the domain name iguser.mycompany.com, then you will specify Admin DN as cn=administrator,cn=users,dc=iguser,dc=mycompany,dc=com).
c. In the Password field, enter the Active Directory administrator account password.
d. Leave the other settings at the default values.
5. In the Finding user entries pane, do the following:
a. In the Base DN field, enter the domain name (for example, if your Active Directory has the domain name iguser.mycompany.com, then you will specify Base DN dc=iguser,dc=mycompany,dc=com).
b. In the Filter field, enter cn=<USER>.
Step 1.3: Configure
the authentication realm1. In the Pulse Connect Secure main page menu, click Users, and then select User Realms > New User Realms. The New Authentication Realm page appears.
2. In the New Authentication Realm page, do the following:
a. In the Name field, enter an authentication realm name, for example, IdentityGuard_Realm.
b. In the Servers pane, do the following:
– In the Authentication field, select Entrust IdentityGuard.
– In the User Directory/Attribute field, select Same as above.
3. Click Save Changes.
Step
2.1: Add the LDAP user role mapping1. In the Pulse Connect Secure main page menu, click Users, and then select Users Realms > LDAP. The LDAP page appears.
2. Click the Role Mapping tab. The Role Mapping page appears
3. Click New Rule. The Role Mapping Rule page appears.
4. In the Role Mapping Rule page, do the following:
a. In the Name field, enter a rule name; for example, User_rule.
b. In the Rule: If username pane, enter * next to the drop-down list.
c. In the then assign these roles, select Users.
d. Click Add.
5. Click Save Changes.
Step 2.2: Add
Identity as a Service user role mapping
1. In the Pulse Connect Secure home page menu, click Users and then select User Realms > Entrust IdentityGuard. The User Realm page appears.
2. Click the Role Mapping tab. The Role Mapping page appears
3. Click New Rule. The Role Mapping Rule page appears.
4. In the Role Mapping Rule page, do the following:
a. In the Name field, enter a rule name; for example, User_rule.
b. In the Rule: If username pane, enter * next to the drop-down list.
c. In the then assign these roles, select Users.
d. Click Add.
5. Click Save Changes.
Step 2.3: Configure
a user role1. Click the Users tab and navigate to select Users Role > New User Role. The New Role page appears.
2. In the Name field, enter a role name.
3. In the Options pane, select the Session Options, UI Options, and Pulse Secure client check boxes.
4. In the Access features pane, select the Web and VPN Tunneling check boxes.
5. Click Save Changes.
Step
3.1: Configure signing in policies1. Click the Authentication tab and navigate to select Signing In > Sign-in Policies. The Signing In page appears.
2. Click New URL. The New Sign-In Policy page appears.
3. In the New Sign-In Policy page, do the following:
a. In the User Type field, select Users.
b. In the Sign-in URL field, enter */.
c. In the Sign-in page field, select Default sign-in page.
d. Leave the other settings at their default values.
4. In the Authentication Realm field, do the following:
a. Select User picks from a list of authentication realms option.
b. In the Available Realm field, select the authentication realm configured in the section, Configure the authentication realm in the section, Configure the AAA clients and authentication realm, for example, Identity as a Service_Realm.
c. Click Add.
5. Click Save Changes.
Step 3.2: Configure
resource policies1. Click the Users tab and navigate to select Resource Policies > VPN Tunneling > Access Control. The VPN Tunneling Access Control page appears.
2. Click New Policy. The New Policy page appears.
3. In the Name field, enter a name, for example, VPN Tunneling Policy.
4. In the Resources field, enter *:*.
5. In the Roles pane, select Policy applies to ALL roles.
6. In the Action pane, select Allow access.
7. Click Save Changes at the bottom of the Pulse Secure main page. You are returned to the VPN Tunneling Access Control page.
8. Click the Connection Profiles tab to configure the SSL VPN profiles. The VPN Tunneling Connection Profile page appears.
9. Click New Profile. The New Profile page appears.
10. In the New Profile page, do the following:
a. In the Name field, enter a name, for example, SSL_VPN.
b. In the IPv4 address assignment pane:
Select DHCP server and enter the DHCP server IP address, or
Select IPv4 address pool and enter the assignable IPv4 address ranges for the client.
c. Scroll down until you see SSL in the Connection Settings pane, and select SSL.
d. Scroll down until you see the DNS Settings pane. Select Manual DNS Settings.
e. In the Primary DNS field, enter the IP address of the DNS server.
11. Click Save Changes.
Step 3.3: Configure
IP address assignment1. Click the System tab and navigate to select Network > VPN Tunneling. The Network VPN Tunneling page appears.
2. In the IP Address field, enter the subnet IP address, for example 172.30.20.0/24, and click Add.
3. In the VPN Tunnel Server IP Address field, enter a static IP address to access the SSL VPN from the web browser or Pulse Secure client.
4. Click Save.
Configure the
Pulse Secure clientConfigure Pulse Secure Client on client PC
1. Open a Web browser on the client computer.
2. Enter the VPN Tunnel Server IP Address, for example <https://172.30.20.15>. You are presented with the Pulse Secure login window.
3. Enter the Identity as a Service user name and password.
4. Click Sign In. You are prompted to respond to the Identity as a Service challenge.
5. In the Response field, enter the Grid response using your Entrust grid card.
6. Click Sign In. The Pulse Secure User Portal page appears.
7. Under the Client Application Session, click Start. The installer download page appears.
8. Double-click to open the downloaded Pulse Secure Client.
9. You are prompted to install the Pulse Secure Client.
10. Click Next to proceed with the installation.
Step
5.1: Add Pulse Secure to Identity as a Service
Note: Entrust recommends that when multiple RADIUS applications are configured that each RADIUS application is given a unique shared secret.
Integrate a RADIUS client
1. Click
> Security > Applications. The Applications
page appears.
2. Click Add. The Select an Application Template page appears.
3. Under RADIUS and VPN Integrations, click Pulse Secure. The Add Pulse Secure page appears.
4. Optional: Edit the Application Name.
5. Optional. Enter a Description for your application.
6. Optional. Add a custom application logo as follows:
a. Click 
next
to Application Logo. The Upload
Logo dialog box appears.
b. Click 
to select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box displays your selected image.
d. If required, resize your image.
e. Click OK.
7. Click Next. The Setup page appears.
8. Click Add to next to Hosts to add the host name of the VPN server. The RADIUS agent receives the request on this host. The RADIUS Agent on the Gateway determines the RADIUS application the request is for based on the host name and port.
9. Enter the host name in the Host dialog box and then click OK. Repeat this step to add more host names.
10. In the Port field, enter the port on which the RADIUS agent accepts messages.
Tip: Do not enter 8443 as the port number for this application. Port 8443 is used by the Entrust Identity Enterprise agent in your Gateway.
Attention: The RADIUS agent
uses the host name that sent a request and the port number that it
received the request from to determine which RADIUS application made
the request. Because of that:
–Two RADIUS applications with the same port value cannot share any
host names.
–Two RADIUS applications that have one or more matching host names
must have different port values.
11. In the Shared Secret field, enter the shared secret that is used by your VPN server. This is the RADIUS secret shared between your VPN server and the RADIUS server. The shared secret value must match a shared secret in your RADIUS client.
12. From the Select RADIUS Agent drop-down list, select the name of the Gateway containing the RADIUS agent to which this application will be assigned.
13. Optional: From the Select RADIUS Attribute for IP Address drop-down list, select the RADIUS attribute that corresponds to your IP location.
14. In the Challenge Response Queue Max Time field, set the number of seconds that the RADIUS agent waits for a response to first-factor authentication. The default value is 180 seconds.
15. In the Challenge Response Queue Max Size field, set the maximum number of second-factor challenge requests allowed in the queue of your RADIUS application. The default value is 1000 requests. The maximum value is 10,000.
16. In the Request Cache Timeout field, set the number of seconds to cache requests. The default value is 10 seconds.
17. From the Character Set drop-down list, select the character set used to decode and encode string values (including the user ID and password values) in RADIUS messages. The options are UTF-8 and ISO-8859-1.
18. Optional: Select Log RADIUS messages to enable RADIUS message logging. When enabled, messages for the RADIUS agent are logged to the same log file as the gateway logs.
19. Optional:
Enable the Authentication Settings.
Select Enable Push Authentication Fallback if you want to authentication to fallback to another authenticator in the event of a failure. If required, set the Push Authentication Fallback Timeout to the number of minutes before the push authentication times out.
Select When authenticating the user will be asked to select their second-factor authenticator. When selected, after the user responds to the first-factor challenge, they are prompted to select their second-factor authenticator. The list of available second-factor authenticators is set by the resource rule.
The following is a list of supported strings matched to the authentication types:
Grid: grid
Knowledge-based Authentication: kba
One-time password: email, sms, voice
Smart Credential Push: scpush
Temporary Access Code: tac
Token: token
Token push: push
Select Indicate if requests must include the message-authenticator attribute for incoming messages to include the message-authenticator attribute for incoming messages.
Select Indicate if requests must include the message-authenticator attribute for outgoing messages to include the message-authenticator attribute for outgoing messages.
Select Remove domain from user ID for incoming requests to remove the domain value from the user ID during authentication when the user ID provided by the RADIUS client is in the format domain\username and the user ID in IDaaS is in the format username.
Select Indicate if Active Directory password authentication requests are handled by the same Gateway Instance that initiated the request to require that Active Directory password authentication and change requests that are initiated as part of the RADIUS authentication are handled by any Gateway Instance in the same Gateway cluster that initiated it. If disabled, the request is handled by any Gateway Instance.
Select Enable one-step multi-factor authentication. When enabled, the user enters their user ID and then their password and token response in the password field. If you select this option, second factor authenticators available in the resource rule are limited to token and temporary access code.
Enter the One-step multi-factor authentication security token length. This is the length of the token or temporary access code response if you enable one-step multi-factor authentication.
20. Optional.
Add Response Attributes. Response attributes are
returned to the RADIUS application after successful authentication.
Use this setting to configure RADIUS attributes to return information
such as the user's group information to the VPN server.
When adding response attributes, you optionally add group filters. For example:
Example:
Users in IDaaS may belong to one of the following groups CANADA,
US, UK, FRANCE.
The VPN server wants the FilterID attribute returned from the IDaaS
RADIUS agent to be the value NA or EUROPE, depending on whether
the user is in NA (Canada, US) or Europe (UK, France).
To do this, use a RADIUS attribute filter for the FilterID attribute
with a Groups value with the following filters:
- match CANADA, replace NA
- match US, replace NA
- match UK, replace EUROPE
- match FRANCE, replace EUROPE
Set the Response Attributes as follows:
Click
Add. The Add
a Response Attribute
dialog box appears.
Select the RADIUS Attribute ID from the drop-down list. The option you select depends on your VPN vendor.
Select the Value Type from the drop-down list.
To return a static value specific in the RADIUS attribute definition, select Static and enter a Value in the field and then click Add.
To return the user’s group membership, select Group and then optionally do the following:
Click Add to add filters.
Enter the Match and the Replace attribute filters.
Click Add to add more attribute filters.
If you add multiple filters, you can drag and drop them in order of preference.
Select Stop after matching filter if you only want one the filter to return one value. Using the example above, if you want NA to have preference over Europe, make sure to list Canada and US in the list of filters.
Multiple Values Per Attribute, enter the Value Separator and then click Add.
Note: If a user belongs to more
than one group, you can either add a separate attribute to your
RADIUS response for each group or you can combine all of the groups
into a single attribute. For example, if the user belongs to G1,G2,G3
then you would
- return a RADIUS response with three attributes
OR
- return a RADIUS response with one attribute and a value like
“G1,G2,G3” where the , is defined in the Value Separator setting
or a value like “G1 G2 G3” where the Value Separator is defined
as a space.
Attention: The default group separator is a space. If you have group names that are separated by a space, use another separator, such as a comma.
Repeat these steps to add more response attributes.
21. Optional: Configure the EAP Settings to set up the application to use the EAP RADIUS authentication protocol.
a. Select EAP Enabled to allow the RADIUS application to accept EAP messages.
– When enabled, authentication messages with EAP content are treated as EAP requests. The application can accept only EAP authentication requests.
– When disabled, incoming authentication requests are processed by the RADIUS application as a standard RADIUS authentication request (even if the request includes EAP content). In this case, the application can accept only standard RADIUS authentication requests.
b. Select the EAP Protocol from the drop-down list. The options are PEAPv0 with MS-CHAPv2 and PEAPv1 with GTC.
This setting defines the type of EAP authentication protocol that is performed on EAP requests received by the RADIUS application. Consult the configuration requirements of your VPN server to determine which EAP protocol to select.
c. Select Return MPPE Keys to include the MPPE (Microsoft Point-to-Point Encryption) recv and mppe send keys in the Access-Accept message returned during a successful EAP authentication. The setting is enabled by default.
d. Select Use PEAPv1 label when calculating MPPE Keys to use the PEAPv1 label when calculating the mmpe recv and mppe send keys.
e. Leave the Minimum TLS Version, Maximum TLS Version and Allow Weak Ciphers at the default settings unless you have an older VPN and need to configure these settings to allow older versions of TLS or weaker ciphers to interoperate with older VPN servers that do not support the latest versions.
22. Configure the Deprecated Settings if your RADIUS application is connected to a Gateway version older than 3.0. These values are only required for backwards compatibility.
a. Select Token OTP Only, Password with second-factor, or No first-factor as the Authentication Type. This setting defines the level of authentication required to access a RADIUS application that relies on a gateway RADIUS agent configured before release 3.1.
Note: MSCHAPv2 authentication is not supported when No first-factor authentication is configured for the RADIUS application.
23. Click Submit.
Step 5.2: Protect
Pulse Secure with a resource rule● Resource rules for RADIUS applications only include the Date / Time, Geolocation and Source IP Address condition restriction.
● The Authentication Decision steps that you can select for a RADIUS application resource rule depend on whether the RADIUS application uses EAP RADIUS authentication.
● If the settings of a RADIUS application on Identity as a Service are modified so that the application uses EAP RADIUS authentication, or the type of EAP protocol used is changed, the resource rule associated with the RADIUS application is automatically updated.
● RADIUS applications with no EAP support the following second-factor authenticators: knowledge-based authentication, temporary access code, one-time password, grid, hardware/software token, token push, and smart credential push.
● RADIUS applications with RADIUS MSCHAPv2 support only temporary access code and hardware/software token second-factor authenticators.
● When creating a resource rule for a RADIUS application, you can select EXTERNAL+no second-factor.
● RADIUS applications with RADIUS GTC support the following second-factor authenticators: software/hardware token, one time password, grid, temporary access code, knowledge-based authentication.
Create a resource rule to protect access to a RADIUS application
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
Attention: You must maintain the default of all groups if you want to allow external authentication and bypass second-factor authentication for users who do not already exist in Identity as a Service. External Authentication without second-factor is only available to low risk users of RADIUS applications that support External Authentication.
6. Click Next. The Authentication Conditions Settings page appears.
7. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
8. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
9. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
10. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
11. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
12. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
13. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
14. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
15. Define the Location History / Known Locations and Travel Velocity conditions.
The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
16. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
17. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
18. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
19. Click Submit to create the resource rule.
Step
6.1: Test Pulse Secure for one-step authentication1. On the client PC, double-click to open the Pulse Secure Client.
Note: It is assumed that you have already deployed Pulse Secure Client software on the client computer by following the instructions in section, Deploying and configuring Pulse Secure Client.
2. Select the + to add a new SSL connection profile. The Add Connection dialog appears.
3. In the Name field, enter the SSL VPN name.
4. In the Server URL field, enter the Pulse Secure SSL URL, for example, https://172.30.20.15/sslvpn.
5. Click Connect. You are prompted to authenticate.
6. In the User Name field, enter the Identity as a Service user name.
7. In the Passcode field, enter the Identity as a Service Password or Temporary PIN.
8. Click Connect.
9. On the Pulse Secure page, select Connections > Advanced Connection Details.
The following Pulse Secure SSL/ VPN connection details screen appears.
Step 6.2: Test
Pulse Secure VPN for two-step authentication1. On the client PC, double-click to open the Pulse Secure Client.
Note: It is assumed that you have already deployed Pulse Secure Client software to client computer as outlined in the section, Configure the Pulse Secure Client.
2. Select the + to add a new SSL connection profile. The Add Connection dialog appears.
3. In the Name field, enter the SSL VPN name.
4. In the Server URL field, enter the Pulse Secure SSL URL, for example, https://172.30.20.15/sslvpn.
5. Click Connect. You are prompted to authenticate.
6. In the User Name field, enter the Identity as a Service user name.
7. In the Passcode field, enter the Identity as a Service Password or Temp PIN.
8. Click Connect. You are prompted to enter the second-factor authentication response.
9. Enter the second-factor authentication response.
Note: The challenge depends on the type of second factor authentication you have configured in the Entrust IdentityGuard Radius Server.
10. Click Connect. After the connection is complete, the Pulse Secure Client Connections screen appears.
Step 6.3: Test
Pulse Secure using Entrust push authenticationTest using the Entrust Identity app for push authentication
1. Log in with the correct first-factor username/password on your RADIUS client.
2. Open the Entrust Identity app on a mobile device.
3. Unlock (log in) using the identity you want to use to respond to the request.
4. Tap Actions.
5. Review the transaction summary details.
6. Tap Confirm.