Supported
authentication methodsThis technical integration guide describes how to integrate a Fortinet-Fortigate and Identity as a Service. The aim of this integration is to provide strong, second-factor authentication for your Fortinet-Fortigate VPN solution using Identity as a Service.
Note: Some configuration steps may differ from the documentation provided or the steps in this integration guide may not be effective (due to Entrust not having tested and validated with the version you are using). For different versions, this integration guide may still offer a standard base to help fast-track SAML authentication setup for your application, but in the event there are issues, contact support@entrust.com for assistance.
The Fortinet-Fortigate software supports the Identity as a Service authentication methods and authentication protocols listed in the table below. The capabilities may depend on the Identity as a Service configuration, or the setup of other 3rd party authentication resources (Active Directory, for example).
Supported
authentication methodsNote: For Fortinet RADIUS authentications, Entrust suggests using PAP or CHAP authentication for two-step Entrust authentication and MSCHAPV1 or MSCHAPv2 for one-step Entrust token authentication. The EAP authentication protocol is not supported.
| Authentication method | Notes | Supported protocols |
Password |
Password authentication is first-factor authentication with Identity as a Service password feature. |
PAP, CHAP |
RADIUS |
RADIUS authentication is first-factor authentication with a RADIUS server. |
PAP, CHAP |
External |
External authentication is first-factor authentication with an LDAP-compliant directory or a Windows domain controller through Kerberos. |
PAP, CHAP |
Grid |
Two-step authentication only. |
PAP, CHAP |
Token |
Identity as a Service supports response-only tokens. One-step and Two-step authentication (including push). |
PAP, CHAP, MSCHAPv1, MSCHAPv2 |
Temporary Access Code |
Grid or token authentication must be configured. |
PAP, CHAP, MSCHAPv1, MSCHAPv2 |
One-time password |
Two-step authentication only. |
PAP, CHAP |
Knowledge-based questions and answers |
The RADIUS proxy only supports a single question and answer. Two-step authentication only. |
PAP, CHAP |
Mobile Soft Token |
Mobile Soft Token push authentication (supports response-only tokens for second-factor authentication). |
PAP, CHAP |
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.
Complete the following steps to integrate FortiNet-FortiGate VPN with IDaaS:
Before you configure Fortinet-FortiGate and manage the system, you need to connect the unit to a management workstation or network.
Start the Fortinet-FortiGate
configuration utility
Start the Configuration utility in a web browser
1. After you connect the management workstation to the FortiGate management interface, in a Web browser, open the Configuration utility and launch the configuration system by typing the following URL syntax where <https://management_IP_address> is the IP address you configured for FortiGate device management.
2. At the login prompt, enter the default user name admin, and password.
3. The Fortinet FortiGate Web GUI opens, which allows you to configure the unit.
There are three steps to integrate the Fortinet-FortiGate with Entrust Identity as a Service and setup the SSL/IPSec Remote Access VPN. Complete all the steps.
Step 2a: Create
a new RADIUS serverTo use IDaaS authentication with a FortiGate unit, configure one or more RADIUS servers on the FortiGate unit and assign users to a RADIUS server. When a configured user attempts to access the network, the FortiGate unit forwards the authentication request to IDaaS, which matches the username and password remotely. Once authenticated, IDaaS passes the authentication to the FortiGate unit, which then grants the user permission to access the network.
1. In the FortiGate Web console, navigate to User & Device > RADIUS Servers and click Create New. The Create RADIUS Server page appears.
2. In the Create RADIUS Server page, do the following:
a. In the Name field, enter the name of the RADIUS server, for example, IDaaS.
b. In the Primary Server IP/Name field, enter 10.4.21.94.
c. In the Primary Server Secret field, enter the shared secret.
Note: The shared secret must be the same value entered the IDaaS Fortinet-FortiGate application page.
d. For the Authentication Method, click Specify.
e. Select the required authentication method from the Method drop-down menu, for example PAP.
f. Click OK.
Step 2b: Create
a RADIUS userYou need to create user accounts on the FortiGate unit to define the authentication with an external authentication server (RADIUS). There are several different types of user accounts with slightly different methods of authentication.
Create a RADIUS user account
1. In the FortiGate Web console, navigate to User & Device > User Definition and then click Create New. The Users/Groups Creation Wizard appears.
2. Select Remote RADIUS User and then click Next. The RADIUS Server page appears.
3. In the User Name field enter the name of the user.
4. From the RADIUS Server drop-down list, select the RADIUS server you created in the section, Creating a new RADIUS server.
5. Click Next to move to the Contact Info section and then click Next again to go to the Extra Info section.
6. In the Extra info section, turn on Enable User Account and then click Submit.
The RADIUS user is created and is listed in the User Definition page.
Step 2c: Create
a RADIUS user groupCreate a RADIUS user group
1. In the FortiGate Web console, navigate to User & Device > User Groups and then click Create New. The Edit User Group page appears.
2. In the Edit User Group page, do the following:
a. In the Name field enter the group name, for example, RADIUS_users.
b. In the Type option, select Firewall.
c. In the Members section select the user you created in the section, Create a RADIUS user.
d. Click OK.
The RADIUS user group is created and is listed in the User Groups page.
The default timeout is 5 seconds; however, this timeout is insufficient when using Entrust Mobile Soft Token and Mobile Smart Credentials Push. Run following commands from the command line to increase the timeout. The timeout should be greater than Entrust Push timeout settings.
config system global
set remoteauthtimeout 100
end
In any firewall user group, you can enable SSL VPN access and select the web-portal that the users can access. When the user connects to the FortiGate unit through HTTPS on the SSL VPN port (default 10443), the FortiGate unit requests a username and password.
SSL VPN access also requires an SSL VPN security policy (action is SSL VPN) with an identity-based rule enabling access for the user group.
Step 4a: Configure
the SSL VPNConfigure the SSL VPN
1. In the FortiGate Web console, navigate to VPN > SSL-VPN Portals, select full-access and then click Edit. The Edit SSL-VPN Portal page appears.
2. Disable the Split Tunneling, as shown above.
3. Click OK.
4. Navigate to the SSL-VPN Settings.
5. Under Connection Settings, do the following:
a. From the Listen on Interface(s) field, select the external Interface-Internet Connected (WAN).
b. In the Listen on Port field enter 10443.
c. For Restrict Access, select Allow access from any host.
d. From the Server Certificate drop-down menu, select the Fortinate built-in certificate, Fortinet-Factory. Ignore the warning.
6. Under Authentication/Portal Mapping, click Create New. The New Authentication/Portal Mapping page appears.
7. In the New Authentication/Portal Mapping section do the following:
a. Under Users/Groups select the RADIUS users group that you created in the section, Create a RADIUS user group.
b. From the Portal drop-down menu, select full-access from the drop-down list.
c. Click OK.
8. In the Authentication/Portal Mapping section, select web-access for All Other Users/Groups and then click Apply.
Step 4b: Create
an SSL VPN policyCreate an SSL VPN policy
1. In the FortiGate Web console, navigate to Policy & Objects > Firewall Policy and then click Create New. The New Policy page appears.
2. In the New Policy page, do the following:
a. In the Name field enter the name of the policy, for example, SSL-VPN.
b. For the Incoming Interface, select SSL-VPN tunnel interface.
c. For the Outgoing Interface, select Internal Network Interface (LAN).
d. For Source select all and the RADIUSuser group that you created in the section, Create a RADIUS user group.
e. For the Destination Address, select All.
f. For the Schedule, select Always.
g. For the Service, select Always.
h. For the Action, select Accept.
i. Leave the remaining settings at the default values.
3. Click OK.
An IPsec VPN can be configured to accept connections from multiple dynamically addressed peers. You would do this to enable employees to connect to the corporate network remotely. On a FortiGate unit, you create this configuration by setting the Remote Gateway to Dialup User. A VPN tunnel has one end on a local trusted network, and the other end is at a remote location. The remote peer (device) must be authenticated to be able to trust the VPN tunnel. The pre-shared key is used to authenticate each other with IPsec VPN.
Step 5a: Configure
the IPsec VPNConfigure the IPsec VPN
1. In the FortiGate Web console, navigate to VPN > IPsec Wizard. The VPN Wizard launches.
2. In the Name field, enter the VPN name, for example IPsec VPN Name.
3. For the Template Type, select Remote Access.
4. For the Remote Device Type, select the FortiClient.
5. Click Next. The Authentication page appears.
6. In the Authentication page, do the following:
a. For the Incoming Interface, select the FortiGate External Interface-Internet Connected (WAN).
b. For the Authentication Method, select Pre-shared key.
c. Enter the Pre-shared key password.
d. From the User Group drop-down menu, select the RADIUS user group you created in Create a RADIUS user group.
e. Click Next. The Policy and Routing page appears.
7. In the Policy and Routing page, do the following:
a. For the Local Interface, select the FortiGate Internal Interface (LAN).
b. For the Local Address, select All.
c. In the Client
Address Range field, enter the IP address range for VPN client
adapter,
for example, 10.0.0.2-10.0.0.250.
d. In the Subnet Mask field, enter the IP Range, for example, 255.255.255.0.
e. Leave the remaining settings at the default values.
f. Click Next. The Client Options page appears.
8. In the Client Options page, click Next.
9. Click Next. The Review Settings page appears.
10. In the Review Settings page, click Create.
11. An IPsec VPN policy is created automatically during the configuration process. The next step in the configuration process is to modify the IPsec VPN policy.
Step 5b: Modify
the IPsec VPN PolicyModify the IPsec VPN policy
1. In the FortiGate Web console, navigate to Policy & Objects, Firewall Policy.
2. Select the IPsec VPN Policy and click Edit. The Edit Policy page appears.
3. In Edit Policy page, change the Source field to ALL and then click OK.
Download the FortiClient software from the Fortinet web and install on it on a Client Computer. After installing the FortiClient, you need to add a VPN connection.
Step 6a: Add
the FortiClient SSL VPN connectionAdd the FortiClient SSL VPN connection
1. Launch the FortiClient software and click Configure VPN. The New VPN Connection page appears.
2. In New VPN Connection page, select the SSL-VPN tab and do the following:
a. In the Connection Name field, enter the name for the connection, for example, SSL_VPN.
b. In the Remote Gateway field, enter the IP address for the FortiGate External interface IP (WAN).
c. Click the Customize port checkbox and enter the port number 10443.
d. Select the Prompt on Login option for Authentication.
e. Leave the remaining settings at the default values.
3. Click Apply and then click Close.
Step
6b: Add an IPsec VPN connectionAdd the FortiClient IPsec VPN connection
1. Launch the FortiClient software and select Add a new connection from Settings drop-down list. The New VPN Connection page appears.
2. In the New VPN Connection page, select the IPsec VPN tab and do the following:
a. In the Connection Name field, enter the name for the connection, for example, IPsec_VPN.
b. In the Remote Gateway field, enter the IP address for the FortiGate External interface IP (WAN).
c. From the Authentication Method drop-down menu, select Pre-shared key and enter the same key you created in the section, Configure the IPsec VPN.
d. Select the Prompt on Login option for Authentication (XAuth).
e. Leave the remaining settings at the default values.
3. Click Apply and then click Close.
Add Fortinet-FortiGate
to Identity as a ServiceNote: 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 Fortinet. The Add Fortinet 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.
Add
a resource rule to protect Fortinet-FortiGateBefore you begin, note the following regarding authentication methods:
● PAP: Supports all IDaaS authentication methods.
● MSCHAP v1 and MSCHAP v2: For MSCHAPv1 and MSCHAPv2 support, modify the IDaaS resource rule to skip password and the first-factor to software/hardware token and temporary access code.
● 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.
Test the authentication
using FortiClient SSL VPN1. Launch the FortiClient software and select SSL-VPN from the Connection drop-down menu.
2. Enter the RADIUS Username and Password, then click Connect.
3. Enter a response to the grid challenge, then click OK.
The user authenticated successfully and a SSL VPN Connection is established.
Test the authentication
using FortiClient IPsec VPN1. Launch the FortiClient software and select IPsec-VPN from the Connection drop-down menu.
2. Enter the RADIUS Username and Password, then click Connect.
3. Enter a response to the token challenge, then click OK.
The user authenticated successfully and the IPsec VPN connection is established.
Test using
mobile soft token authentication1. Log in with the correct first-factor username/password on the FortiClient SSL or IPsec-VPN Connection.
2. Open the Entrust Identity app on your mobile device.
3. Click the Actions button at the bottom of the screen if you have not received a new transaction notification.
4. Click Confirm.