Ivanti Connect Secure SAML Single Sign-On (SSO)
Ivanti Connect Secure offers SP-initiated SAML SSO (for SSO access directly through the Ivanti Connect Secure web application). The following is an overview of the steps required to configure the Ivanti Connect Secure Web application for single sign-on (SSO) via SAML.
-
Prepare Ivanti Connect Secure for single sign-on (see Ivanti Connect Secure requirements for SSO).
-
In the Identity Administration portal, add the application and configure application settings.
Once the application settings are configured, complete the user account mapping and assign the application to one or more roles.
-
Configure the Ivanti Connect Secure application for single sign-on.
To configure Ivanti Connect Secure for SSO, copy settings from the Application Settings page in the Identity Administration portal and paste them into the Ivanti Connect Secure website. For more information, see Configure Ivanti Connect Secure on its website.
After you are done configuring the application settings in the Identity Administration portal and the Ivanti Connect Secure application, users are ready to authenticate using the CyberArk Cloud Directory.
Ivanti Connect Secure requirements for SSO
Before you configure the Ivanti Connect Secure web application for SSO, make sure you have a signed certificate. You can either download one from the Identity Administration portal or use your organization’s trusted certificate.
Set up the certificates for SSO
To establish a trusted connection between the web application and CyberArk Identity, you need to have the same signing certificate in both the application and the application settings in the Identity Administration portal.
If you use your own certificate, you upload the signing certificate and its private key in a .pfx or .p12 file to the application settings in the Identity Administration portal. You also upload the public key certificate in a .cer or .pem file to the web application.
What you need to know about Ivanti Connect Secure
Each SAML application is different. The following table lists features and functionality specific to Ivanti Connect Secure.
Capability |
Supported? |
Support details |
Web browser client |
Yes |
|
Mobile client |
No |
|
SAML 2.0 |
Yes |
|
SP-initiated SSO |
Yes |
Users may go directly to a supplied Ivanti Connect Secure URL and then use CyberArk Identity SSO to authenticate. |
IdP-initiated SSO |
No |
|
Force user login via SSO only |
No |
Administrators and users can still log in with a user name and password after SSO is enabled. |
Separate administrator login after SSO is enabled |
No |
|
User or Administrator account lockout risk |
No |
User name and password login is always available. |
Automatic user provisioning |
No |
|
Self-service password |
N/A |
|
Access restriction using a corporate IP range |
Yes |
You can specify an IP Range in the Identity Administration portal Policy page to restrict access to the application. |
Configure Ivanti Connect Secure in the Identity Administration portal
-
In the Identity Administration portal, click Apps, then click Add Web Apps.
The Add Web Apps screen appears.
-
On the Search tab, enter the partial or full application name in the Search field and click the search icon.
-
Next to the application, click Add.
-
In the Add Web App screen, click Yes to confirm.
Identity Administration portal adds the application.
-
Click Close to exit the Application Catalog.
The application that you just added opens to the Application Settings page.
The description of how to choose and download a signing certificate in this document might differ slightly from your experience. See Choose a certificate file for the latest information. -
Configure the following:
Field
Required or optional
Set it to
What you do
Assertion Consumer Service URL
Required
https://YOUR-JUNIPER-VPN-ACS-URL
Copy the value from the Ivanti Connect Secure Service Provider metadata and paste it here. This is set the Fully Qualified Domain Name (FQDN) for your instance of the Ivanti Connect Secure server.
Identity Provider Entity Id
Required
CyberArk Identity automatically generates the content for this field.
Copy this value and then paste it into the Identity Provider Entity Id field in Auth. Servers > SAML Server > Settings page on the Ivanti Connect Secure website.
SA Entity Id
Required
Value from the Ivanti Connect Secure website.
Copy the value in the Auth. Servers > SAML Server > Settings > SA Entity Id field on the Ivanti Connect Secure website and paste it here.
Identity Provider Single Sign On Service URL
Required
CyberArk Identity automatically generates the content for this field.
Copy this value and then paste it into the Identity Provider Single Sign On Service URL field in Auth. Servers > SAML Server > Settings page on the Ivanti Connect Secure website.
Download Signing Certificate
Required
CyberArk Identity automatically generates the content.
Download the signing certificate and then click Upload Certificate on the Auth. Servers > SAML Server > Settings page on the Ivanti Connect Secure website to upload the certificate.
To use a certificate with a private key (pfx file) from your local storage, see below.
If you replace the certificate, download the signing certificate again and upload the new file to the Ivanti Connect Secure website.
-
(Optional) On the Application Settings page, click Enable Derived Credentials for this app on enrolled devices (opens in built-in browser) to use derived credentials on enrolled mobile devices to authenticate with this application.
-
On the Application Settings page, expand the Additional Options section and specify the following settings:
Option
Description
Application ID
Configure this field if you are deploying a mobile application that uses the mobile SDK. CyberArk Identity uses the Application ID to provide single sign-on to mobile applications. Note the following:
The Application ID has to be the same as the text string that is specified as the target in the code of the mobile application written using the mobile SDK. If you change the name of the web application that corresponds to the mobile application, you need to enter the original application name in the Application ID field.
There can only be one SAML application deployed with the name used by the mobile application.
The Application ID is case-sensitive and can be any combination of letters, numbers, spaces, and special characters up to 256 characters.
Show in User app list
Select Show in User app list to display this web application in the user portal. (This option is selected by default.)
If this web application is added only to provide SAML for a corresponding mobile app, deselect this option so the web application won’t display for users in the user portal.
Security Certificate
These settings specify the signing certificate used for secure SSO authentication between CyberArk Identity and the web application. Just be sure to use a matching certificate both in the application settings in the Identity Administration portal and in the application itself. Select an option to change the signing certificate.
Use existing certificate
When selected the certificate currently in use is displayed. It’s not necessary to select this option—it’s present to display the current certificate in use.
Use the default tenant signing certificate
Select this option to use CyberArk Identity standard certificate. This is the default setting.
Use a certificate with a private key (pfx file) from your local storage
Select this option to use your organization’s own certificate. To use your own certificate, you must click Browse to upload an archive file (.p12 or .pfx extension) that contains the certificate along with its private key. If the file has a password, you must enter it when prompted.
Upload the certificate from your local storage prior to downloading the IdP metadata or the Signing Certificate from the Applications Settings page. If the IdP metadata is available from a URL, be sure to upload the certificate prior to providing the URL to your service provider.
-
(Optional) On the Description page, you can change the name, description, and logo for the application. For some applications, the name cannot be modified.
The Category field specifies the default grouping for the application in the user portal. Users have the option to create a tag that overrides the default grouping in the user portal.
-
On the User Access page, select the role(s) that represent the users and groups that have access to the application.
When assigning an application to a role, select either Automatic Install or Optional Install:
-
Select Automatic Install for applications that you want to appear automatically for users.
-
If you select Optional Install, the application doesn’t automatically appear in the user portal and users have the option to add the application.
-
-
(Optional) On the Policy page, specify additional authentication controls for this application.
-
Click Add Rule.
The Authentication Rule window displays.
-
Click Add Filter on the Authentication Rule window.
-
Define the filter and condition using the drop-down boxes. For example, you can create a rule that requires a specific authentication method when users access CyberArk Identity from an IP address that is outside of your corporate IP range. Supported filters are:
Filter
Description
IP Address
The authentication factor is the computer’s IP address when the user logs in. This option requires that you have configured the IP address range in Settings, Network, Secure Zones.
The authentication factor is the cookie that is embedded in the current browser by CyberArk Identity after the user has successfully logged in.
Day of Week
The authentication factor is the specific days of the week (Sunday through Saturday) when the user logs in.
Date
The authentication factor is a date before or after which the user logs in that triggers the specified authentication requirement.
Date Range
The authentication factor is a specific date range.
Time Range
The authentication factor is a specific time range in hours and minutes.
Device OS
The authentication factor is the device operating system.
Browser
The authentication factor is the browser used for opening CyberArk Identity user portal.
Country
The authentication factor is the country based on the IP address of the user computer.
Risk Level
The authentication factor is the risk level of the user logging on to user portal. For example, a user attempting to log in to CyberArk Identity from an unfamiliar location can be prompted to enter a password and text message (SMS) confirmation code because the external firewall condition correlates with a medium risk level. This Risk Level filter, requires additional licenses. If you do not see this filter, contact CyberArk Identity support. The supported risk levels are:
Non Detected -- No unexpected activities are detected.
Low -- Some aspects of the requested identity activity are unexpected. Remediation action or simple warning notification can be raised depending on the policy setup.
Medium -- Many aspects of the requested identity activity are unexpected. Remediation action or simple warning notification can be raised depending on the policy setup.
High -- Strong indicators that the requested identity activity is anomaly and the user's identity has been compromised. Immediate remediation action, such as MFA, should be enforced.
Unknown -- Not enough user behavior activities (frequency of system use by the user and length of time user has been in the system) have been collected.
Managed Devices
The authentication factor is the designation of the device as “managed” or not. A device is considered “managed” if it is managed by CyberArk Identity, or if it has a trusted certificate authority (CA has been uploaded to tenant).
For the Day/Date/Time related conditions, you can choose between the user’s local time and Universal Time Coordinated (UTC) time.
-
Click the Add button associated with the filter and condition.
-
Select the profile you want applied if all filters/conditions are met in the Authentication Profile drop-down.
The authentication profile is where you define the authentication methods. If you have not created the necessary authentication profile, select the Add New Profile option. See Create authentication profiles.
-
Click OK.
-
-
(Optional) In the Default Profile (used if no conditions matched) drop-down, you can select a default profile to be applied if a user does not match any of the configured conditions.
If you have no authentication rules configured and you select Not Allowed in the Default Profile dropdown, users will not be able to log in to the service.
-
Click Save.
If you have more than one authentication rule, you can prioritize them on the Policy page. You can also include JavaScript code to identify specific circumstances when you want to block an application or you want to require additional authentication methods. For more information, see Application access policies with JavaScript.
If you left the Apps section of the Identity Administration portal to specify additional authentication control, you will need to return to the Apps section before continuing by clicking Apps at the top of the page in the Identity Administration portal. -
On the Account Mapping page, configure how the login information is mapped to the application’s user accounts.
The options are as follows:
-
Use the following Directory Service field to supply the user name: Use this option if the user accounts are based on user attributes. For example, specify an Active Directory field such as mail or userPrincipalName or a similar field from the CyberArk Cloud Directory.
-
Everybody shares a single user name: Use this option if you want to share access to an account but not share the user name and password. For example, some people share an application developer account.
-
Use Account Mapping Script: You can customize the user account mapping here by supplying a custom JavaScript script. For example, you could use the following line as a script:
LoginUser.Username = LoginUser.Get('mail')+'.ad';
The above script instructs CyberArk Identity to set the login user name to the user’s mail attribute value in Active Directory and add ‘.ad’ to the end. So, if the user’s mail attribute value is Adele.Darwin@acme.com then CyberArk Identity uses Adele.Darwin@acme.com.ad. For more information about writing a script to map user accounts, see the SAML application scripting.
-
-
(Optional) On the Advanced page, you can edit the script that generates the SAML assertion, if needed. In most cases, you don’t need to edit this script. For more information, see the SAML application scripting.
-
(Optional) On the Changelog page, you can see recent changes that have been made to the application settings, by date, user, and the type of change that was made.
-
(Optional) Click Workflow to set up a request and approval work flow for this application.
See Manage application access requests for more information.
-
Click Save.
See CyberArk-issued derived credentials for more information.
Configure Ivanti Connect Secure on its website
-
In your web browser, go to the Ivanti Connect Secure URL and sign in with your administrator credentials.
-
Navigate to Authentication >Auth. Servers on the Ivanti Connect Secure website and select SAML Server from the New drop-down menu and then click New Server.
-
Provide a name for the server and click 2.0 for the SAML Version.
-
On the Auth. Servers > SAML Server > Settings page, configure the following settings:
Field
What you do
SA Entity Id
Copy this value and paste it into the field in the Identity Administration portal > Application Settings.
Configuration Mode
Click Manual.
Identity Provider Entity Id
Copy the contents of the Identity Provider Entity Id field in the Identity Administration portal > Application Settings and paste it here.
Identity Provider Single Sign On Service URL
Copy the contents of the Identity Provider Single Sign On Service URL field in the Identity Administration portal > Application Settings and paste it here.
User Name Template
Leave this option blank.
Allowed Clock Skew
Enter 10.
SSO Method:
Artifact
Post
Select Post.
Download the Signing Certificate from the Application Settings page in the Identity Administration portal (if you haven’t done so already).
Click Choose File to upload the security certificate you downloaded from Application Settings page in the Identity Administration portal.
If you use your own certificate be sure to upload it in the Application Settings page in the Identity Administration portal.
Select Device Certificate for Signing
Not applicable
Select Device Certificate for Encryption
Not applicable
Metadata Validity
Set this to a value appropriate for your instance.
Do Not Publish SA Metadata
Do not enable this option.
Download Metadata
Not applicable
-
Click Save Changes.
For more information about Ivanti Connect Secure
For more information about configuring Ivanti Connect Secure for SSO, contact Ivanti Connect Secure support.