--- title: Users Configuration slug: ps/help/en_us/nsa/22x/nsa-ics/ag/1013 docTags: createdAt: 2026-07-22T09:12:33.633Z --- - [Configuring User Realm](docId\:q2SWzExiSq6OxuG47Wuyb) - [Configuring User Role](docId\:q2SWzExiSq6OxuG47Wuyb) - [Resource Profiles](docId\:q2SWzExiSq6OxuG47Wuyb) - [Resource Policies](docId\:q2SWzExiSq6OxuG47Wuyb) - [Ivanti Secure Access Client Connections](docId\:q2SWzExiSq6OxuG47Wuyb) - [Enterprise Onboarding](docId\:q2SWzExiSq6OxuG47Wuyb) ## Configuring User Realm The user realm configuration associates the authentication server data and MDM server data with user roles. To configure user realm: 1. Log into the NSA as a Tenant Admin. 2. From the Ivanti Connect Secure menu, click the **Gateway > Gateway List** and then select any standalone ICS Gateway and Cluster node. 3. Navigate to **Users > User Realms**. A list of user realms is displayed. Use the Search bar at the top to filter the results list. For each column, click the arrow icon adjacent to the column name to sort in ascending or descending order. 4. In the User Realms page, click the Add icon. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Sg8SkHcgi-SkFMRdQtmuY_userrealmcreate.png" alt="img/user_realm_create.png" position="flex-start" size="78" width="784" height="1030" initialPath="img/user_realm_create.png" githubPath="img/user_realm_create.png" darkWidth="784" darkHeight="1030" showCaption="false"} 5. Enter a name and description for the realm. 6. Under Servers, specify: - A server to use for device authorization (optional). - A RADIUS accounting server to use to track when a user signs-in and signs-out of the Ivanti Connect Secure (optional). - A directory/attribute server to use for retrieving user attribute and group information for role mapping rules and resource policies. (optional) - An authentication server to use for authenticating users who sign in to this realm. 7. If you want to submit secondary user credentials to an SSO-enabled resource or enable two-factor authentication to access the device, select Additional authentication server. Then: - Select FallBack Authentication Server form drop down. This acts as a fallback authentication method. If the primary authentication method such as certificate, LDAP, or Active Directory fails, users can use TOTP as a backup method. This option is available only on User Realms. - Select End session if authentication against this server fails if you want to control access to the system based on the successful authentication of the user's secondary credentials. If selected, authentication fails if the user's secondary credentials fail. :::Paragraph{indent="1"} **Mask Static Password: **A check box has been added to mask static password. This new check box by default is disabled and any new upgrade with this feature will show the UI as unchecked. Once password is masked, there is no way the password can be unmasked and only way would be to edit and set a new password. This option can be done for both Admin realm and User Realm. ::: - Select Password is specified by user on sign-in page if you want to prompt the user to manually submit his password to the secondary server during the sign-in process. Otherwise, if you want to automatically submit a password to the secondary server, enter static text or a valid variable in the predefined field. - Select Username is specified by user on sign-in page if you want to prompt the user to manually submit his username to the secondary server during the sign-in process. Otherwise, if you want to automatically submit a username to the secondary server, enter static text or a valid variable in the predefined as field. By default, the system submits the username session variable, which holds the same username used to sign in to the primary authentication server. - Select the name of the secondary authentication server. 8. If you want to use dynamic policy evaluation for this realm, select **Dynamic policy evaluation** to enable an automatic timer for dynamic policy evaluation of this realm’s authentication policy, role mapping rules, and role restrictions: - Use the **Refresh interval** option to specify how often you want Connect Secure to perform an automatic policy evaluation of all currently signed-in realm users. - Select **Refresh roles** to also refresh the roles of all users in this realm. - Select **Refresh resource policies** to also refresh the resource policies for all users in this realm. - Click **Refresh Now** to manually evaluate the realm’s authentication policy, role mapping rules, role restrictions, user roles, and resource policies of all currently signed-in realm users. 9. Select one of the following options: - **Apply IP and/or Location based restrictions** - Allows or/and denies users access from all listed IP addresses or/and Geo-Locations. - **Allow users to sign in from any IP address and Location** - Allows users to sign in from any IP address and Location to satisfy the access management requirement. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WdoBeieBt0PxGD2rdIW0Y_userrealmsourceip799x211.png" position="flex-start" size="80" width="799" height="211" initialPath="img/user_realm_sourceip_799x211.png" githubPath="img/user_realm_sourceip_799x211.png" darkWidth="799" darkHeight="211" showCaption="false" indent="1"} :::Paragraph{listStyleType="disc" indent="2"} Select either **Allow **to allow users to sign in from the specified Location, or **Deny **to prevent users from signing in from the specified Location and click **Add**. ::: :::Paragraph{listStyleType="disc" indent="2"} Select the **Location**. ::: :::Paragraph{listStyleType="disc" indent="2"} Select **Configure Location based restrictions** that specifies whether to allow or deny users access from all of the Locations. based on their settings. ::: :::Paragraph{indent="1"} To specify access from a Location, select **Apply IP and/or Location based restrictions**, and then: ::: :::Paragraph{indent="1"} And/Or ::: :::Paragraph{listStyleType="disc" indent="2"} Select either **Allow **to allow users to sign in from the specified IP address, or **Deny **to prevent users from signing in from the specified IP address and click **Add**. ::: :::Paragraph{listStyleType="disc" indent="2"} Enter the **IP address** and **netmask**. ::: :::Paragraph{listStyleType="disc" indent="2"} Select **Configure IP based restrictions** that specifies whether to allow or deny users access from all of the listed IP addresses, based on their settings. ::: :::Paragraph{indent="1"} To specify access from an IP address, select **Apply IP and/or Location based restrictions**, and then: ::: 10. Click **Save Changes** to create the realm. :::hint{type="info"} Ivanti recommends Multi factor Authentication (MFA) for all realms to minimizes authentication related security vulnerabilities. If not configured with MFA, realms will be listed in red color with (\*\*) asterisk next to realm name. ::: ## Configuring User Role A user role is an entity that defines user session parameters, personalization settings, and enabled access features. You can customize a user role by enabling specific access features, defining Web, application, and session bookmarks, and configuring session settings for the enabled access features. To add a new user role: 1. Log into the NSA as a Tenant Admin. 2. From the Ivanti Connect Secure menu, click the **Gateway > Gateway List** and then select any standalone ICS Gateway and Cluster node. 3. Navigate to **Users > User Roles**. A list of user roles is displayed. Use the Search bar at the top to filter the results list. For each column, click the arrow icon adjacent to the column name to sort in ascending or descending order. 4. In the User Roles page, click the Add icon. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/IjKW6tdF7FtXTeTknzRdB_userrolecreate568x576.png" alt="img/user_role_create.png" position="flex-start" size="57" width="568" height="576" initialPath="img/user_role_create_568x576.png" githubPath="img/user_role_create_568x576.png" darkWidth="568" darkHeight="576" showCaption="false"} 5. Enter a name and optionally a description. 6. Under Options: - Select the **VLAN/Source IP** option to apply the role settings configured on the General > VLAN/Source IP page. - Select the **Session Options** option to apply the role settings in the General > Session Options page to the role. - Select the **UI Options** option to apply the role settings in the General > UI Options page to the role. 7. Under Access features, select the features you want to enable for the role. Options include: - Web - intermediate Web URLs through the Content Intermediation Engine. - Files, Windows - resource profile that controls access to resources on Windows server shares. - Secure Application Manager (Windows version or Java version) - provides secure, application-level remote access to enterprise servers from client applications. - Terminal Services - enable terminal emulation sessions on a Windows terminal server, Citrix NFuse server, or Citrix Metaframe server. - Virtual Desktops - enable virtual desktop session using the VDI architecture. - HTML5 Access - enable HTML5 session for RDP connection, telnet connection, SSH session or VNC connection. - VPN Tunneling - provides secure, SSL-based network-level remote access to all enterprise application resources using the system. - Secure Mail - enables automatic synchronization with an Exchange server (ActiveSync) and e-mail encryption for iOS devices that have the Ivanti Secure Access Client. 8. Click **Save Changes** to apply the settings to the role. ## Resource Profiles A resource profile contains all of the resource policies, role assignments, and end-user bookmarks required to provide access to an individual resource. Resource profiles simplify resource configuration by consolidating the relevant settings for an individual resource into a single page within the admin console. The system comes with two types of resource profiles: - Standard resource profiles enable you to configure settings for a variety of resource types, such as web sites, client/server applications, directory servers, and terminal servers. When you use this method, you choose a profile type that corresponds to your individual resource and then provide details about the resource. - Resource profile templates enable you to configure settings for specific applications. When you use this method, you choose a specific application (such as the Citrix NFuse version 4.0). Then, the system pre-populates a variety of values for you based on your chosen application and prompts you to configure additional settings as necessary. Resource profiles are an integral part of the access management framework, and therefore are available on all Ivanti Connect Secure products. However, you can only access resource profile types that correspond to your licensed features. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/xy3REpb5O4qwC_pnk-JN1_respro613x396.png" alt="img/respro.png" position="flex-start" size="61" width="613" height="396" initialPath="img/respro_613x396.png" githubPath="img/respro_613x396.png" darkWidth="613" darkHeight="396" showCaption="false"} ### Web Resource Profile To Create new Web Application Resource Profiles: 1. Log into the NSA as a Tenant Admin. 2. From the Ivanti Connect Secure menu, click the **Gateway > Gateway List** and then select any standalone ICS Gateway and Cluster node. 3. Navigate to **Users > Resource Profiles >Web**. A list of resource profiles is displayed. Use the Search bar at the top to filter the results list. For each column, click the arrow icon adjacent to the column name to sort in ascending or descending order. 4. Click ‘**+**’ and select the Profile Template from drop down. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/phjanqa2Psf4CIg9BSauM_webmain569x145.png" alt="img/webmain.png" position="flex-start" size="57" width="569" height="145" initialPath="img/webmain_569x145.png" githubPath="img/webmain_569x145.png" darkWidth="569" darkHeight="145" showCaption="false"} 1. Enter a unique **Name** and optionally a **Description** for the profile. ### Citrix Storefront Server If you have the Citrix StoreFront 31. and above, you can create a Web template to allow users to access Citrix applications without the need for a Citrix client. Users must have one of the following browser versions (or later) to support HTML5 and Websockets: - Internet Explorer 10 - Safari 6 - Google Chrome 23 - Mozilla Firefox 17 If **Citrix resource profile** selected as Profile Template, then 1. Enter the URL of the **Citrix StoreFront Web** server in the **Base URL** field. Use the format: \[protocol://]host\[:port]\[/path]. The system uses the specified URL to define the default bookmark for the Citrix resource profile. 2. Under **Citrix Settings**, select the **ICA Client Access** option. Admin can either choose to go with the HTML5 way of delivery or can choose to deliver ICA over CTS/PSAM/HTML5 Access clients. If admin chooses the ICA over CTS/PSAM/HMTL5 Access, the corresponding ACL should be created and when ICS rewrites ICA content it should launch the appropriate client. Add the Number of servers/applications and Citrix Ports which require ICA client access. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/9b3NgRsbB7IV9ChYDnfT1_ctrix1576x477.png" alt="img/ctrix1.png" position="flex-start" size="58" width="576" height="477" initialPath="img/ctrix1_576x477.png" githubPath="img/ctrix1_576x477.png" darkWidth="576" darkHeight="477" showCaption="false"} 3. Click **Add Autopolicy**, **Web Access Control** or **Single Sign-on** check box to create a policy and click **Add Selected**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/wtUchKpVBiKYiNkSZTZdY_ctrix2580x218.png" alt="img/ctrix2.png" position="flex-start" size="58" width="580" height="218" initialPath="img/ctrix2_580x218.png" githubPath="img/ctrix2_580x218.png" darkWidth="580" darkHeight="218" showCaption="false"} 4. Under **Web Access Control**, click ‘**+**’ specific Resource under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. By default, the system automatically creates a policy that enables access to the resource and all of its subdirectories. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Cm0ZV7MU6WOgAqw50p1Sk_ctrix4570x277.png" alt="img/ctrix4.png" position="flex-start" size="57" width="570" height="277" initialPath="img/ctrix4_570x277.png" githubPath="img/ctrix4_570x277.png" darkWidth="570" darkHeight="277" showCaption="false"} 5. Under **Single Sign-on**, select the **POST the following data** check box and specify the application's sign-in page in **Resource** field and In **Post URL** field, specify the absolute URL where the application posts the user's credentials. - In the Resource field, specify the application's sign-in page, such as: http\://my.domain.com/public/login.cgi. Wildcard characters are not supported in this field. - In the Post URL field, specify the absolute URL where the application posts the user's credentials, such as: http\://yourcompany.com/login.cgi. 6. Select the **Deny direct login for this resource** check box if you do not want to allow users to manually enter their credentials in a sign-in page. Users may see a sign-in page if the form POST fails. 7. Select the **Allow multiple POSTs to this resource** check box if you want to send POST and cookie values to the resource multiple times if required. 8. Optionally, click ‘+’ specify the **Label, Name, Value, and select User modifiable, click**Save Changes\*\*. - Label - The name used to identify the data. - Name - The name used to identify the data in the Value field. The back-end application should expect this name. - Value - The value to post to the form for the specified Name. You can enter static data, a system variable, or system session variables containing username and password values. - User modifiable? - Select Not modifiable to prevent users from changing the information in the Value field. Select User CAN change value to allow users to specify data for a back-end application. Select User MUST change value if users must enter additional data to access a back-end application. 9. To post header data to the specified URL select the **Send the following data as request headers** check box. 10. Specify the **Resources** to which this policy applies. 11. Optionally, click ‘**+**’ specify the **Header name** and **Value** and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ACMregZTo8_MnxckkBdYG_ctrix3.png" alt="img/ctrix3.png" position="flex-start" size="78" width="781" height="855" initialPath="img/ctrix3.png" githubPath="img/ctrix3.png" darkWidth="781" darkHeight="855" showCaption="false"} ### Hosted Java Applet :::hint{type="info"} For ICS 25.x Gateways, this feature is deprecated and will be removed in the near future. ::: The Java applet upload feature enables you to store the Java applets of your choice directly on the device without employing a separate Web server to host them. When you use this feature, you simply upload the applets to the device (along with additional files that the applets reference) and create a simple Web page through the system that references the files. Then, the system intermediates the Web page and Java applet content using its Content Intermediation Engine. For example, you might want to use the system to intermediate traffic between an IBM AS/400 system on your network and individual 5250 terminal emulators on your users' computers. To configure the system to intermediate this traffic, obtain the 5250 terminal emulator's Java applet. Then you can upload this applet to the system and create a simple Web page that references the applet. After you create the Web page through the system, it creates a corresponding bookmark that users can access through their home pages. If **Hosted Java applet** is selected as Profile Template, then 1. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/kRDbg-6grmcSleAoYEJ5__hjava1576x555.png" alt="img/hjava1.png" position="flex-start" size="58" width="576" height="555" initialPath="img/hjava1_576x555.png" githubPath="img/hjava1_576x555.png" darkWidth="576" darkHeight="555" showCaption="false"} 2. Click ‘**+**’ to add an applet to this list. :::hint{type="info" indent="3"} If you replace an existing archive, make sure that the new applet archive contains all of the necessary files for the applet to successfully launch and run. If the associated HTML for the applet refers to files that do not exist in the new archive, then the applet will not function correctly. ::: :::Paragraph{listStyleType="decimal" indent="2"} Enter **Name** to identify the applet. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} Click the text field to browse to the applet that you want to upload. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} Select the **Uncompress archive file** check box if the file that you selected is an archive that contains the applet. Click **OK**. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/r5WOREGajwy50e1uk-T-2_javaapp527x73.png" alt="img/javaapp.png" position="flex-start" size="53" width="527" height="73" initialPath="img/javaapp_527x73.png" githubPath="img/javaapp_527x73.png" darkWidth="527" darkHeight="73" showCaption="false" indent="3"} :::hint{type="info"} When you select an applet in the Java Applets dialog box, you are loading third-party software onto the Ivanti product. By clicking OK, you are agreeing to the following terms on behalf of yourself (as purchaser of the equipment) or the organization that purchased the Ivanti product, as applicable. ::: 3. Click **Add Autopolicy**, select **Java Access Control to enable access** if your Java applets need to make socket connections. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/M60XyDkFwcbOWrC4e3G5N_hjava2580x210.png" alt="img/hjava2.png" position="flex-start" size="58" width="580" height="210" initialPath="img/hjava2_580x210.png" githubPath="img/hjava2_580x210.png" darkWidth="580" darkHeight="210" showCaption="false"} 4. Click ‘**+**’ specific **Resource** under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/IS8DH96GFJlePpwPTMWfn_hjava3172x167.png" alt="img/hjava3.png" position="flex-start" size="17" width="172" height="167" initialPath="img/hjava3_172x167.png" githubPath="img/hjava3_172x167.png" darkWidth="172" darkHeight="167" showCaption="false"} 5. Select the **Sign applets with uploaded code-signing certificate(s)** to use a single code-signing certificate to resign all Java applets. 6. Click **Save Changes**. ### Microsoft RDWeb :::hint{type="info"} For ICS 25.x Gateways, this feature is deprecated and will be removed in the near future. ::: A Microsoft RDWeb template is a resource profile that controls access to the published desktops and applications based on HTML5. Microsoft RDWeb templates significantly reduce the configuration time by consolidating configuration settings into one place and by pre-populating a variety of resource policy settings. If **Microsoft RDWeb** resource profile selected as Profile Template, then 1. Enter the URL of the Microsoft RDWeb server in the **Base URL** field. 2. Click **Add Autopolicy**, **Web Access Control** check box to create a policy and click **Add Selected**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/bu203-zJD4L5KBBMobzrX_mrdweb2471x142.png" alt="img/mrdweb2.png" position="flex-start" size="47" width="471" height="142" initialPath="img/mrdweb2_471x142.png" githubPath="img/mrdweb2_471x142.png" darkWidth="471" darkHeight="142" showCaption="false"} 3. Under **Web Access Control**, click ‘**+**’ specific **Resource** under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/dUylg4uF0NZJLUTGte-ka_mrdweb1614x452.png" alt="img/mrdweb1.png" position="flex-start" size="61" width="614" height="452" initialPath="img/mrdweb1_614x452.png" githubPath="img/mrdweb1_614x452.png" darkWidth="614" darkHeight="452" showCaption="false"} ### Microsoft OWA Versions :::hint{type="info"} For ICS 25.x Gateways, this feature is deprecated and will be removed in the near future. ::: A Microsoft Outlook Web Access (OWA) template is a resource profile that controls access to the application and configures OWA settings as necessary. OWA templates significantly reduce your configuration time by consolidating configuration settings into one place and by prepopulating a variety of resource policy settings for you depending on the type of setup you select. The system supports intermediating traffic to Microsoft OWA through a Web rewriting resource profile template, JSAM, PSAM, and VPN Tunneling. This topic describes how to configure access using the Web rewriting template. The prepopulated values vary depending on the version of OWA you select and are based on the most common deployment of the servers. If any of the **Microsoft OWA** Versions are selected as Profile Template, then 1. Enter the URL of the OWA resource to which you want to control access In the **Base URL** box. 2. Under **OWA settings**, select **Security Settings** and Select **Prevent download of attachments** to prohibit users from downloading attachments to their systems. 3. Select **Prevent upload of attachments** to prevent users from transmitting (uploading) attachments to the system. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/dQGAshv2bp2ZrF-X-lJN__mowa1562x520.png" alt="img/mowa1.png" position="flex-start" size="56" width="562" height="520" initialPath="img/mowa1_562x520.png" githubPath="img/mowa1_562x520.png" darkWidth="562" darkHeight="520" showCaption="false"} 1. Click **Add Autopolicy**, check box to create a policy and click **Add Selected**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/x_GYsaREkdxP8icmw-rpd_mowa2576x320.png" alt="img/mowa2.png" position="flex-start" size="58" width="576" height="320" initialPath="img/mowa2_576x320.png" githubPath="img/mowa2_576x320.png" darkWidth="576" darkHeight="320" showCaption="false"} 1. Under **Web Access Control**, click ‘**+**’ specific **Resource** under the Base URL. Enter the full **URL** of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ymlZ4V7U1vmXZmkFOl1dR_mowa3576x552.png" alt="img/mowa3.png" position="flex-start" size="58" width="576" height="552" initialPath="img/mowa3_576x552.png" githubPath="img/mowa3_576x552.png" darkWidth="576" darkHeight="552" showCaption="false"} 1. Under **Single Sign-on**, **select the SSO** from drop down and specify the application's sign-in page in **Resource** field and select user's **credentials**. 2. Check **Fallback to NTLM V1** to enable fallback option and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/zOHFVZ7L4zXEdN5Na-w5K_mowa4574x336.png" alt="img/mowa4.png" position="flex-start" size="57" width="574" height="336" initialPath="img/mowa4_574x336.png" githubPath="img/mowa4_574x336.png" darkWidth="574" darkHeight="336" showCaption="false"} 1. Under **Caching**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/PX7jKmoOMpx3VbpDWpJ3W_mowa5569x550.png" alt="img/mowa5.png" position="flex-start" size="57" width="569" height="550" initialPath="img/mowa5_569x550.png" githubPath="img/mowa5_569x550.png" darkWidth="569" darkHeight="550" showCaption="false"} 1. Under **Web Compression**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop-down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/oaaSHtcaYU8kU55e3HGT7_mowa6572x471.png" alt="img/mowa6.png" position="flex-start" size="57" width="572" height="471" initialPath="img/mowa6_572x471.png" githubPath="img/mowa6_572x471.png" darkWidth="572" darkHeight="471" showCaption="false"} 1. Under **Client Authentication**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Certificate** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/6ACefCs3uu-5CHYQ0zWQV_mowa7573x587.png" alt="img/mowa7.png" position="flex-start" size="57" width="573" height="587" initialPath="img/mowa7_573x587.png" githubPath="img/mowa7_573x587.png" darkWidth="573" darkHeight="587" showCaption="false"} ### Lotus iNotes Versions :::hint{type="info"} For ICS 25.x Gateways, Lotus iNotes 7 and Lotus iNotes 8 are deprecated and will be removed in the near future. ::: A Lotus iNotes template is a resource profile that controls access to the Web application and configures iNotes settings as necessary. Lotus iNotes templates significantly reduce your configuration time by consolidating settings into one place and by prepopulating a variety of resource policy settings for you depending on the type of setup you select. The system supports intermediating traffic to Lotus iNotes through a Web rewriting resource profile template, JSAM, PSAM, and VPN Tunneling. This topic describes how to configure access using the Web rewriting template. The prepopulated values vary depending on the version of iNotes you select and are based on the most common deployment of the servers. If any of the **Lotus iNotes** versions resource profile are selected as Profile Template, then 1. Enter the **URL** of the Lotus iNotes resource to which you want to control access In the Base URL box. 2. Under **iNotes settings**, select **Caching Settings**, select **Allow caching on client** to let Web browsers store non-user data, such as Javascript and CSS files, on a user's machine. Select **Minimize caching on client to allow** the system to send a cache-control\:no-store header or a cache-control\:no-cache header based on the user's Web browser and content type. This is the same as smart caching. The Allow caching on client option caches content that the backend iNotes server typically caches. This caching option improves performance by using the cached content instead of retrieving the content from the server the next time the page displays. The Minimize caching on client option provides security by sending a cache-control\:no-store header or a cache-control\:no-cache header to either not store content or to re-validate the cached content each time it is requested. With both caching option, you can choose to either allow or prevent the uploading or downloading of attachments. 3. Select **Prevent download of attachments** to prohibit users from downloading attachments to their systems. 4. Select **Prevent upload of attachments** to prevent users from transmitting (uploading) attachments to the system. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/3zHlkskxgaeprcFbklDx2_lotus1580x479.png" alt="img/lotus1.png" position="flex-start" size="58" width="580" height="479" initialPath="img/lotus1_580x479.png" githubPath="img/lotus1_580x479.png" darkWidth="580" darkHeight="479" showCaption="false"} 5. Click **Add Autopolicy**, check box to create a policy and click **Add Selected**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/4WlCq8izYTSUop-yacWvM_lotus2557x317.png" alt="img/lotus2.png" position="flex-start" size="56" width="557" height="317" initialPath="img/lotus2_557x317.png" githubPath="img/lotus2_557x317.png" darkWidth="557" darkHeight="317" showCaption="false"} 6. Under **Web Access Control**, click ‘**+**’ specific **Resource** under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mGvVas32jjFvDPoBm6Dmb_mowa3567x543.png" alt="img/mowa3.png" position="flex-start" size="57" width="567" height="543" initialPath="img/mowa3_567x543.png" githubPath="img/mowa3_567x543.png" darkWidth="567" darkHeight="543" showCaption="false"} 7. Under **Single Sign-on**, select the **SSO** from drop down and specify the application's sign-in page in **Resource** field and select user's **Credentials** and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/w6WYXYZLx6Vg_miabLu6y_lotus3570x276.png" alt="img/lotus3.png" position="flex-start" size="57" width="570" height="276" initialPath="img/lotus3_570x276.png" githubPath="img/lotus3_570x276.png" darkWidth="570" darkHeight="276" showCaption="false"} 8. Under **Caching**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/PREsNORXpkRGccPlZS2Yt_mowa5579x560.png" alt="img/mowa5.png" position="flex-start" size="58" width="579" height="560" initialPath="img/mowa5_579x560.png" githubPath="img/mowa5_579x560.png" darkWidth="579" darkHeight="560" showCaption="false"} 9. Under **Web Compression**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/_mPFjbwYUq6uYxkW4a8B6_mowa6574x473.png" alt="img/mowa6.png" position="flex-start" size="57" width="574" height="473" initialPath="img/mowa6_574x473.png" githubPath="img/mowa6_574x473.png" darkWidth="574" darkHeight="473" showCaption="false"} 10. Under **Client Authentication**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Certificate** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/TGnt6M5yajreDz5o44tC3_mowa7578x592.png" alt="img/mowa7.png" position="flex-start" size="58" width="578" height="592" initialPath="img/mowa7_578x592.png" githubPath="img/mowa7_578x592.png" darkWidth="578" darkHeight="592" showCaption="false"} ### Microsoft Sharepoint A Microsoft Sharepoint template is a resource profile that controls access to the application and configures Sharepoint settings as necessary. Microsoft Sharepoint templates significantly reduce your configuration time by consolidating configuration settings into one place and by pre-populating a variety of resource policy settings for you depending on the type of setup you select. The system supports intermediating traffic to Microsoft Sharepoint through a Web rewriting resource profile template, JSAM, PSAM, and VPN Tunneling. This topic describes how to configure access using the Web rewriting template. If **Microsoft Sharepoint** resource profile selected as Profile Template, then 1. Enter the URL of the Sharepoint resource to which you want to control access In the Base URL box.Use the format: *\[protocol://]host\[:port]\[/path]*. 2. Under Sharepoint Settings, select **Allow in-line editing of documents within explorer view** to allow users to modify files displayed in the explorer view. 3. Click ‘**+**’ to add the Resource and click **Save Resource**. 4. Enter the number of minutes a persistent cookie resides on a user's computer before it expires in the **Persistent cookie** timeout box. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/MqhUKr3FJH0rqTcmjlwc0_msharep1573x508.png" alt="img/msharep1.png" position="flex-start" size="57" width="573" height="508" initialPath="img/msharep1_573x508.png" githubPath="img/msharep1_573x508.png" darkWidth="573" darkHeight="508" showCaption="false"} 5. Click **Add Autopolicy**, check box to create a policy and click **Add Selected**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/9hxyfPWeb-uWK5jdb8cM__msharep2583x367.png" alt="img/msharep2.png" position="flex-start" size="58" width="583" height="367" initialPath="img/msharep2_583x367.png" githubPath="img/msharep2_583x367.png" darkWidth="583" darkHeight="367" showCaption="false"} 6. Under **Web Access Control**, click ‘**+**’ specific **Resource** under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/iQ2YAYN-OEfLZWGkVX96K_mowa3577x553.png" alt="img/mowa3.png" position="flex-start" size="58" width="577" height="553" initialPath="img/mowa3_577x553.png" githubPath="img/mowa3_577x553.png" darkWidth="577" darkHeight="553" showCaption="false"} 7. Under **Single Sign-on**, select the **SSO** from drop down and specify the application's sign-in page in **Resource** field and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Ta8YVsNFCQImoDHSaEtnx_msharep3579x234.png" alt="img/msharep3.png" position="flex-start" size="58" width="579" height="234" initialPath="img/msharep3_579x234.png" githubPath="img/msharep3_579x234.png" darkWidth="579" darkHeight="234" showCaption="false"} 8. Under **Caching**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/JyRiLIyptrF4VxIbZ_3nz_mowa5571x552.png" alt="img/mowa5.png" position="flex-start" size="57" width="571" height="552" initialPath="img/mowa5_571x552.png" githubPath="img/mowa5_571x552.png" darkWidth="571" darkHeight="552" showCaption="false"} 9. Under Rewriting Options, select the Rewriting Options: - **Passthrough Proxy** - Select this option to specify Web applications for which the Content Intermediation Engine performs minimal intermediation. - **No rewriting (use WSAM)** - Select this option to intermediate content using PSAM instead of the Content Intermediation Engine. Then, specify the application server for which you want to intermediate content. (At minimum, you need to click Add in order to intermediate content to and from the server that the system extracts from the Web access control policy). - **No rewriting (use JSAM)** - Select this option to intermediate content using JSAM instead of the Content Intermediation Engine. Then, specify the application server for which you want to intermediate content. (At minimum, you need to click Add in order to intermediate content to and from the server that the system extracts from the Web access control policy). - **No rewriting** - Select this option to automatically create a selective rewriting policy for the autopolicy's URL, thereby configuring the system to not intermediate any content to and from the resource. For example, you may choose this option if you do not want the system to intermediate traffic from web sites that reside outside of the corporate network, such as yahoo.com. If you select this option, you do not have to configure any additional rewriting settings. If **Passthrough Proxy** is selected: :::Paragraph{listStyleType="decimal" listRestartPolite="1" indent="2"} Choose the way in which you want to enable the passthrough proxy feature: ::: :::Paragraph{listStyleType="disc" indent="3"} **Use virtual hostname** - If you choose this option, specify a hostname alias for the application server. When the system receives a client request for the application server hostname alias, it forwards the request to the specified application server port in the Base URL field. ::: :::Paragraph{listStyleType="disc" indent="3"} **Use IVE port** - If you choose this option, specify a unique port in the range 11000-11099. The system listens for client requests to the application server on the specified port and forwards any requests to the application server port specified in the Base URL field. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} Select the **Rewrite XML** check box if you want to rewrite URLs contained within XML content. If this option is disabled, the system passes the XML content "as is" to the server. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} Select the **Rewrite external links** check box if you want to rewrite all the URLs presented to the proxy. If this option is disabled, the system rewrites only those URLs where the hostname is configured as part of the passthrough proxy policy. ::: :::Paragraph{listStyleType="decimal" listStart="4" indent="2"} Select the **Block cookies from being sent to the browser** check box if you want to block cookies destined for the client's browser. The system stores the cookies locally and sends them to applications whenever they are requested. ::: :::Paragraph{listStyleType="decimal" listStart="5" indent="2"} Select the **Host-Header forwarding** check box if you want to pass the hostname as part of the host header instead of the actual host identifier. click **Save Changes**. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/xFKTaJJKxuDDe3kfYaeiV_msharep4538x347.png" alt="img/msharep4.png" position="flex-start" size="54" width="538" height="347" initialPath="img/msharep4_538x347.png" githubPath="img/msharep4_538x347.png" darkWidth="538" darkHeight="347" showCaption="false" indent="3"} If **No rewriting (use WSAM)** is selected :::Paragraph{listStyleType="decimal" indent="2"} Create a rewriting autopolicy and select No rewriting (use WSAM). ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} In the **Destination** field, specify resources for which PSAM secures client/server traffic between the client and the system. By default, the system extracts the correct server from the Web access control policy. You may choose to use this server as-is, modify it, and/or add new servers to the list. When specifying a server, specify the hostname (the wild cards '\*' or '?' are accepted) or an IP/netmask pair. Specify multiple ports for a host as separate entries. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} Click **Save Changes**. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WntJxej1Df23uI8MUPijo_msharep5583x499.png" alt="img/msharep5.png" position="flex-start" size="58" width="583" height="499" initialPath="img/msharep5_583x499.png" githubPath="img/msharep5_583x499.png" darkWidth="583" darkHeight="499" showCaption="false"} If **No rewriting (use JSAM)** options is selected: :::Paragraph{listStyleType="decimal" indent="2"} In the **Server Name** field, enter the DNS name of the application server or the server IP address. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} In the **Server Port** field, enter the port on which the remote server listens for client connections. ::: :::Paragraph{listStyleType="disc" indent="3"} For example, to forward Telnet traffic from a remote machine, specify port 23 for both the client port (on which JSAM listens) and the server port (on which the Telnet server listens). ::: :::Paragraph{listStyleType="disc" indent="3"} To enable drive mapping to this resource, enter 139 as the server port. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} In the **Client Loopback IP** field, provide a static loopback address. If you do not provide a static IP loopback address, the system assigns an IP loopback address dynamically. ::: :::Paragraph{listStyleType="decimal" listStart="4" indent="2"} In the **Client Port** field, enter the port on which JSAM should listen for client application connections. Typically, the local port value is the same value as the server port; the local port value usually only differs for Linux or Macintosh users who want to add applications for port forwarding that use ports under 1024. To enable drive mapping to this resource, enter 139 as the server port. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ADaSTyWrBCeil2XiQEYJL_msharep6537x667.png" alt="img/msharep6.png" position="flex-start" size="54" width="537" height="667" initialPath="img/msharep6_537x667.png" githubPath="img/msharep6_537x667.png" darkWidth="537" darkHeight="667" showCaption="false" indent="3"} 10. Select **Launch JSAM** to automatically start JSAM when the system encounters the Base URL. 11. Click **Save Changes**. If **No rewriting** options is selected, then only selective rewriting resource policy is created. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/EqMwKrJkblMTyIhUv2oV2_msharep7580x196.png" alt="img/msharep7.png" position="flex-start" size="58" width="580" height="196" initialPath="img/msharep7_580x196.png" githubPath="img/msharep7_580x196.png" darkWidth="580" darkHeight="196" showCaption="false"} 12. Under **Web Compression**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Action** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Tll4l8i9By44z3TzVWvxd_mowa6575x474.png" alt="img/mowa6.png" position="flex-start" size="57" width="575" height="474" initialPath="img/mowa6_575x474.png" githubPath="img/mowa6_575x474.png" darkWidth="575" darkHeight="474" showCaption="false"} 13. Under **Client Authentication**, click ‘**+**’ and specify the resources to which this policy applies in the **Resource** filed and select the **Certificate** from drop down and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ueLWFFtJuBge74AVz53y1_mowa7570x584.png" alt="img/mowa7.png" position="flex-start" size="57" width="570" height="584" initialPath="img/mowa7_570x584.png" githubPath="img/mowa7_570x584.png" darkWidth="570" darkHeight="584" showCaption="false"} ### File Browsing To create a Windows file browsing resource profile: 1. Navigate to **Users > Resource Profiles > Files**. 2. Click ‘**+**’. Or select an existing profile from the list. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/7VvFVlSTZy51pPlor8Fpj_file1582x120.png" alt="img/file1.png" position="flex-start" size="58" width="582" height="120" initialPath="img/file1_582x120.png" githubPath="img/file1_582x120.png" darkWidth="582" darkHeight="120" showCaption="false"} 3. Select **Windows** from the Type list. 4. Enter a unique **Name** and optionally a **Description** for the resource profile. (This name becomes the default session bookmark's name.) 5. Enter the **Server name** to share. 6. If required, select to **show All AutoPolicy** types. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/t2aNFTfgoVuKtzWwwCcsQ_file2567x499.png" alt="img/file2.png" position="flex-start" size="57" width="567" height="499" initialPath="img/file2_567x499.png" githubPath="img/file2_567x499.png" darkWidth="567" darkHeight="499" showCaption="false"} 7. Check **Autopolicy Windows File Access Control** to set the file access control. 8. Click ‘**+**’ to add specific **Resource**. Enter the full URL of the resource, select **Allow**, **Deny** or **Read Only**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/NauIs85WkehuhZoez0E-j_file3572x655.png" alt="img/file3.png" position="flex-start" size="57" width="572" height="655" initialPath="img/file3_572x655.png" githubPath="img/file3_572x655.png" darkWidth="572" darkHeight="655" showCaption="false"} 9. Check **Autopolicy: Windows File Compression** to set the file access control. 10. Click ‘**+**’ to add specific resource. Enter the full URL of the resource, select **Compress** or **Do not Compress**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/sap9bHnCydoq_fV-70_rs_file4576x437.png" alt="img/file4.png" position="flex-start" size="58" width="576" height="437" initialPath="img/file4_576x437.png" githubPath="img/file4_576x437.png" darkWidth="576" darkHeight="437" showCaption="false"} 11. Under **Autopolicy: Windows Server Single Sign-On**, select the **SSO** from drop down and specify the application's sign-in page in **Resource** field and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/aDrgDJR_l5H0Wl47s7wGF_file5578x207.png" alt="img/file5.png" position="flex-start" size="58" width="578" height="207" initialPath="img/file5_578x207.png" githubPath="img/file5_578x207.png" darkWidth="578" darkHeight="207" showCaption="false"} ### Terminal Services Terminal Services resource profile configuration instructions vary depending on whether you want to configure access to a Windows terminal server (which requires an RDP client) or Citrix terminal server (which requires an ICA client). Furthermore, if you choose to configure access to a Citrix server using a custom ICA file, you include many of your configuration settings in the ICA file itself and therefore do not need to configure them through the system. If you configure access to a Citrix server using the default ICA file on the system, however, you must configure additional settings. You may want to create multiple bookmarks for the same terminal services resource in order to provide easy access to multiple applications. For instance, the server defined in your resource profile may provide access to multiple applications (such as Siebel and Outlook). To easily provide access to each of these applications, you can create resource profile bookmarks to each. Or, you may want to use multiple bookmarks to configure single sign-on to one application, but not another. :::hint{type="info"} Enabling or disabling Terminal Services does not affect VDI functionality. ::: To create a terminal services resource profile: 1. Navigate to **Users > Resource Profiles > Terminal Services**. 2. Click ‘**+**’. Or select an existing profile from the list. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WDBZlc1ghB5jz_qpJ1GLm_term1576x137.png" alt="img/term1.png" position="flex-start" size="58" width="576" height="137" initialPath="img/term1_576x137.png" githubPath="img/term1_576x137.png" darkWidth="576" darkHeight="137" showCaption="false"} 1. If **Windows Terminal Services** is selected from the Type list. 1. Enter a unique Name and optionally a description for the resource profile. (This name becomes the default session bookmark's name.) 2. Specify the server and port to which this resource profile should connect in the Host field. When entering the server, you may enter a hostname or IP address. 3. Enter the port on which the terminal server listens in the Server port box. (By default, the system populates this box with port number 3389.) 4. Select the **Create an access control policy allowing Terminal Service access to this server** check box to enable access to the server specified in the Server Port box (enabled by default). 5. If you want to enable intermediation using a Java client, select **Enable Java support** and then specify which Java client the system should use. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/J6e7EvHd1yVwLaR-lS8P__term2533x441.png" alt="img/term2.png" position="flex-start" size="53" width="533" height="441" initialPath="img/term2_533x441.png" githubPath="img/term2_533x441.png" darkWidth="533" darkHeight="441" showCaption="false"} 6. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. 7. Click ‘**+**’ to add an applet to this list. 8. Enter **Name** to identify the applet. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/VrKhbwyl457t-bzVCRG_2_javaapp522x72.png" alt="img/javaapp.png" position="flex-start" size="52" width="522" height="72" initialPath="img/javaapp_522x72.png" githubPath="img/javaapp_522x72.png" darkWidth="522" darkHeight="72" showCaption="false"} 9. Click the text field to browse to the applet that you want to upload. 10. Select the **Uncompress archive file** check box if the file that you selected is an archive that contains the applet. Click **OK**. 11. Select the **Criteria** from the drop down. If the Windows client launches, then this Java applet will not be used. 12. Click **Save Changes**. :::hint{type="info"} When you select an applet in the Java Applets dialog box, you are loading third-party software onto the Ivanti product. By clicking OK, you are agreeing to the following terms on behalf of yourself (as purchaser of the equipment) or the organization that purchased the Ivanti product, as applicable. ::: 1. If **Citrix using default ICA** is selected from the Type list. 1. Enter a unique Name and optionally a description for the resource profile. (This name becomes the default session bookmark's name). 2. Specify the server and port to which this resource profile should connect in the Host field. When entering the server, you may enter a hostname or IP address. 3. Enter the port on which the terminal server listens in the Server port box. (By default, the system populates this box with port number 3389). 4. Select the **Create an access control policy allowing Terminal Service access to this server** check box to enable access to the server specified in the Server Port box (enabled by default). ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/i760xkO_R5heETlRLbSWG_term3521x472.png" alt="img/term3.png" position="flex-start" size="52" width="521" height="472" initialPath="img/term3_521x472.png" githubPath="img/term3_521x472.png" darkWidth="521" darkHeight="472" showCaption="false"} 5. If you want to enable intermediation using a Java client, select **Enable Java support** and then specify which Java client the system should use. :::hint{type="info"} For ICS 25.x Gateways, this option is disabled and will be removed in the near future. ::: 6. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WzZA8KNpEiBO8HiC0gZ7G_javaapp529x73.png" alt="img/javaapp.png" position="flex-start" size="53" width="529" height="73" initialPath="img/javaapp_529x73.png" githubPath="img/javaapp_529x73.png" darkWidth="529" darkHeight="73" showCaption="false"} 7. Click ‘**+**’ to add an applet to this list. 8. Enter **Name** to identify the applet. 9. Click the text field to browse to the applet that you want to upload. 10. Select the **Uncompress archive file** check box if the file that you selected is an archive that contains the applet. Click **OK**. 11. Enter HTML with variables to replace the bookmark. 12. Select the **Criteria** from the drop down. If the Windows client launches, then this Java applet will not be used. 13. Click **Save Changes**. :::hint{type="info"} When you select an applet in the Java Applets dialog box, you are loading third-party software onto the Ivanti product. By clicking OK, you are agreeing to the following terms on behalf of yourself (as purchaser of the equipment) or the organization that purchased the Ivanti product, as applicable. ::: 1. If **Citrix using custom ICA file** is selected from the **Type** list. 1. Specify the ICA file that contains the session parameters that you want use in the Custom ICA File box. Note that you may download and customize the following ICA files from the system. - ICA file that comes with the system-To customize this file, click the Open link, save the file to your local machine, customize the file as required, and upload it back to the system using the Browse option. If you customize this file, you must replace the following parameters in the default.ica file: \, \ and \. - ICA file that you have already associated with the resource profile-To customize this file, click the Current ICA File link, save the file to your local machine, and customize the file as required. Once you make changes, you must upload the revised version using the Browse option. 2. Enter a unique **Name** and optionally a **Description** for the resource profile. (This name becomes the default session bookmark's name.) 3. Select the Autopolicy: Terminal Services Access Control check box. 4. Click '**+**' and Specify the Metaframe servers to which you want to enable access in the **Resource** field. 5. Choose **Allow** to enable access to the specified resource or **Deny** to block access to the specified resource from the **Action** list. Click **Save Changes**. 6. Specify the server and port to which this resource profile should connect in the Host field. When entering the server, you may enter a hostname or IP address. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/P9HiRJIJyNGE6wCP77Yze_term4534x482.png" alt="img/term4.png" position="flex-start" size="53" width="534" height="482" initialPath="img/term4_534x482.png" githubPath="img/term4_534x482.png" darkWidth="534" darkHeight="482" showCaption="false"} 7. If you want to enable intermediation using a Java client, select **Enable Java support** and then specify which Java client the system should use. :::hint{type="info"} For ICS 25.x Gateways, this option is disabled and will be removed in the near future. ::: 8. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WzZA8KNpEiBO8HiC0gZ7G_javaapp529x73.png" alt="img/javaapp.png" position="flex-start" size="53" width="529" height="73" initialPath="img/javaapp_529x73.png" githubPath="img/javaapp_529x73.png" darkWidth="529" darkHeight="73" showCaption="false"} 9. Click ‘**+**’ to add an applet to this list. 10. Enter **Name** to identify the applet. 11. Click the text field to browse to the applet that you want to upload. 12. Select the **Uncompress archive file** check box if the file that you selected is an archive that contains the applet. Click **OK**. 13. Enter **HTML code** with variables to replace the bookmark. 14. Select the **Criteria** from the drop down. If the Windows client launches, then this Java applet will not be used. 15. Click **Save Changes**. 2. If **Citrix Listed Applications** is selected from the Type list: 1. Enter a unique **Name** and optionally a **Description** for the resource profile. (This name becomes the default session bookmark's name.) 2. Enter the IP address and port of the Citrix MetaFrame server where the XML service is running. - You do not need to enter the port number if you are using the default value. The default port is 80 (if SSL is selected, the default port is 443). - You can enter more than one server. If the connection fails on one server, the next server in the list is used. 3. Click the **Use SSL for connecting to Citrix XML Service** check box to send the password through SSL instead of cleartext. Although cleartext is supported, we recommend you always use SSL to avoid any security issues. 4. Enter the **Username**, **Password**, and **Domain** name for connecting to the Citrix Metaframe server where the XML service is running. - You can enter variable credentials such as \ and \. If you use variable credentials, the Subset of selected Applications option is disabled in the Bookmarks window. - When the user accesses the application list, their credentials are submitted to the Citrix XML service, substituting the session context variables \ and \. Only the user's specific applications (as determined by the Citrix administrator) are returned. 5. Select the Autopolicy: Terminal Services Access Control check box. 6. Click '**+**' and Specify the Metaframe servers to which you want to enable access in the **Resource** field. 7. Choose **Allow** to enable access to the specified resource or **Deny** to block access to the specified resource from the **Action** list. Click **Save Changes**. 8. Specify the server and port to which this resource profile should connect in the Host field. When entering the server, you may enter a hostname or IP address. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/4_ss6go6zdYcGPQILe-TU_term5535x409.png" alt="img/term5.png" position="flex-start" size="54" width="535" height="409" initialPath="img/term5_535x409.png" githubPath="img/term5_535x409.png" darkWidth="535" darkHeight="409" showCaption="false"} 9. If you want to enable intermediation using a Java client, select **Enable Java support** and then specify which Java client the system should use. :::hint{type="info"} For ICS 25.x Gateways, this option is disabled and will be removed in the near future. ::: 10. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/Z0THUN0vrINSYN_K0QzZK_javaapp537x74.png" alt="img/javaapp.png" position="flex-start" size="54" width="537" height="74" initialPath="img/javaapp_537x74.png" githubPath="img/javaapp_537x74.png" darkWidth="537" darkHeight="74" showCaption="false"} 11. Click ‘**+**’ to add an applet to this list. 12. Enter **Name** to identify the applet 13. Click the text field to browse to the applet that you want to upload. 14. Select the **Uncompress archive file** check box if the file that you selected is an archive that contains the applet. Click **OK**. 15. Enter **HTML code** with variables to replace the bookmark. 16. Select the **Criteria** from the drop down. If the Windows client launches, then this Java applet will not be used. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/uFghll9JRki0K5etnJpyB_term6503x314.png" alt="img/term6.png" position="flex-start" size="50" width="503" height="314" initialPath="img/term6_503x314.png" githubPath="img/term6_503x314.png" darkWidth="503" darkHeight="314" showCaption="false" indent="1"} :::Paragraph{listStyleType="decimal" indent="2"} Click **Save Changes**. ::: ### Virtual Desktop In addition to standard resource profiles and resource profile templates, you can configure virtual desktops as resource profiles. As with the other resource profiles, a virtual desktop profile contains all of the role assignments and end-user bookmarks required to provide access to an individual resource. Unlike other resource profile types, there is no resource policy to configure for virtual desktops due to the dynamic nature of virtual desktops. The IP address and port of the system is not known until the end user launches a session so dynamic ACLs are used. Icons in the Virtual Desktops section on the end user's home page represent desktops defined by the administrator. Clicking the icon launches the session using the Virtual Desktop Infrastructure (VDI) architecture. The Citrix XenDesktop manages a pool of virtual desktops hosted on virtual machines and provides the connection management to those desktops. A list of XenDesktops is displayed to the end user as bookmarks. When a desktop is selected, the Citrix client is launched and the user can access that desktop. VMware View Manager, formerly VMware VDI, lets you run virtual desktops in a data center that provide end users a single view of all their applications and data in a personalized environment regardless of the device or location they log in from. To configure a Citrix XenDesktop or VMware View Manager profile: 1. Navigate to **Users > Resource Profiles > Virtual Desktops**. 2. Click ‘**+**’ and Select **VMware View Manager** or **Citrix XenDesktop** from the Type drop-down list ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/m83JUZEoppjKG6bIfukAy_vd1539x104.png" alt="img/vd1.png" position="flex-start" size="54" width="539" height="104" initialPath="img/vd1_539x104.png" githubPath="img/vd1_539x104.png" darkWidth="539" darkHeight="104" showCaption="false" indent="1"} 3. Enter a **Name** and **Description** (optional) to identify this profile. 4. Enter the **Name** or **IP address** and port of the connection broker using the format ip\:port. You can enter more than one IP address. Place each address on a separate line. 5. Select the **Use SSL for connecting to the Server** check box if **SSL** is required to connect to the server. 6. Enter the **Username** to connect to the connection broker or use the **\** session variable. 7. Enter the **Variable Password** or **Password** - To use a variable password to connect to the connection broker, select Variable Password and enter the variable in the form of \ or \<[PASSWORD@SEcAuthServer](#)>. - Select Password to use a static password to connect to the connection broker and enter the user credential's password. 8. Enter the **Domain** where the connection broker is located. 9. Click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/ql8uOtNPcJrqiqdZStp-f_vd1535x104.png" alt="img/vd1.png" position="flex-start" size="54" width="535" height="104" initialPath="img/vd1_535x104.png" githubPath="img/vd1_535x104.png" darkWidth="535" darkHeight="104" showCaption="false" indent="1"} 10. If you want to enable intermediation using a Java client, select **Enable Java support** and then specify which Java client the system should use (applicable only if Citrix XenDesktop is selected in type). :::hint{type="info"} For ICS 25.x Gateways, this option is disabled and will be removed in the near future. ::: 11. Select the Java applet that you want to associate with the resource profile from the **Applet to use** list. Or, if the applet that you want to use is not currently available in the list, click **Edit list**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/St1Bsk2JGRsU0ogZRd1-I_javaapp575x79.png" alt="img/javaapp.png" position="flex-start" size="57" width="575" height="79" initialPath="img/javaapp_575x79.png" githubPath="img/javaapp_575x79.png" darkWidth="575" darkHeight="79" showCaption="false"} ### HTML5 Access A HTML5 Access resource profile is a profile that enables users to connect to Remote Desktops or to connect to internal server hosts in the clear using Telnet protocols or to communicate over an encrypted Secure Shell (SSH) session through a Web-based terminal session emulation. The HTML5 license count was based on the number of active HTML5 sessions. The HTML5 licenses will be counted based on the number of active users. Each user will be allowed to access up to five user sessions. To create a HTML5 Access resource profile: 1. Navigate to **Users > Resource Profiles > HTML5 Access**. 2. Click ‘**+**’. **Solution Type** is **Advanced HTML5**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/0hv5qKiewTjOu75MAk4L8_html1570x123.png" alt="img/html1.png" position="flex-start" size="57" width="570" height="123" initialPath="img/html1_570x123.png" githubPath="img/html1_570x123.png" darkWidth="570" darkHeight="123" showCaption="false"} 3. From the Type list, specify the session type (**Windows RDP** or **SSH** or **Telnet**) for this resource profile. If you have selected Advanced HTML5 solution type, you can also specify **VNC** session type. :::hint{type="info"} For ICS 25.x Gateways, the Telnet option is deprecated and will be removed in the near future. ::: 4. Enter a unique **Name** and optionally a **Description** for the resource profile. 5. In the **Host** field, enter the Hostname, IP or user attribute of the server to which this resource profile should connect. 6. In the **Server Port** field, enter the port on which the system should connect to the server. (By default, the system populates this field with port number 3389 if you select Windows RDP, port number 23 if you select Telnet, port number 22 if you select SSH and port number 5900 if you select VNC.) 7. Select the **Create an access control policy for HTML5 access** check box to enable access to the server specified in the Server Port box (enabled by default). 8. Click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/kT3AyW-u4h78jk7rSzf0h_html2460x307.png" alt="img/html2.png" position="flex-start" size="46" width="460" height="307" initialPath="img/html2_460x307.png" githubPath="img/html2_460x307.png" darkWidth="460" darkHeight="307" showCaption="false"} 9. Edit the profile. In the **Roles** tab, select the roles to which the resource profile applies and click **Add**. The selected roles inherit the autopolicy and bookmarks created by the resource profile. If it is not already enabled, the system also automatically enables the HTML5 Access option in the Users > User Roles > Select Role > General > Overview page of the admin console for all of the roles you select. 10. Click **Save Changes**. 11. (Optional) In the Bookmarks tab, modify the default bookmark created by the system and/or create new ones. (By default, the system creates a bookmark to the server defined in the Host field and displays it to all users assigned to the role specified in the Roles tab.) :::hint{type="info"} For ICS 25.x Gateways, the Bookmarks option is deprecated and will be removed in the near future. ::: To configure the external storage for session recordings: 1. Navigate to **Users > Resource Profiles > HTML5 Access > Storage Configuration**. 2. Select *Enable external storage*. 3. Enter the complete storage path to store the session recordings. 4. Enter the **Username** and **Password** required to access the location. 5. Click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/uDKulf0DDJw6hB1Lr8K5I_storage568x237.png" alt="img/storage.png" position="flex-start" size="57" width="568" height="237" initialPath="img/storage_568x237.png" githubPath="img/storage_568x237.png" darkWidth="568" darkHeight="237" showCaption="false"} ### SAM Resource Profiles You can create two types of PSAM resource profiles: - PSAM application resource profiles-These resource profiles configure PSAM to secure traffic to a client/server application. When you create a PSAM application resource profile, the PSAM client intercepts requests from the specified client applications to servers in your internal network. - PSAM destination network resource profiles-These resource profiles configure PSAM to secure traffic to a server. When you create a PSAM destination network resource profile, the PSAM client intercepts requests from processes running on the client that are connecting to the specific internal hosts. When creating PSAM resource profiles, note that the resource profiles do not contain bookmarks. To access the applications and servers that PSAM intermediates, users must first launch PSAM and then launch the specified application or server using standard methods (such as the Windows Start menu or a desktop icon). When you enable JSAM or PSAM through Web rewriting autopolicies in the Users > Resource Profiles > Web Applications/Pages page of the admin console, the system automatically creates JSAM or PSAM autopolicies for you. You can only view these SAM policies through the appropriate Web resource profile-not through the SAM resource profile pages of the admin console. ### Client Applications PSAM To create a PSAM application resource profile: 1. Navigate to **Users > Resource Profiles > SAM > Client Applications**. 2. Click ‘**+**’. choose **PSAM** from the Type list 3. From the Application list, select one of the options. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mCdIrKcKy6XjO3PzX-pxq_ca1570x100.png" alt="img/ca1.png" position="flex-start" size="57" width="570" height="100" initialPath="img/ca1_570x100.png" githubPath="img/ca1_570x100.png" darkWidth="570" darkHeight="100" showCaption="false"} :::Paragraph{listStyleType="disc" indent="2"} **Custom** - When you select this option, you must manually enter your custom application's executable file name (such as telnet.exe). Additionally, you may specify this file's path and MD5 hash of the executable file (although it is not required that you specify the exact path to the executable). If you enter an MD5 hash value, PSAM verifies that the checksum value of the executable matches this value. If the values do not match, PSAM notifies the user that the identity of the application could not be verified and does not forward connections from the application to the system. ::: :::Paragraph{listStyleType="disc" indent="2"} **Lotus Notes** - When you select this option, PSAM intermediates traffic from the Lotus Notes fat client application. ::: :::Paragraph{listStyleType="disc" indent="2"} **Microsoft Outlook** - When you select this option, PSAM intermediates traffic from the Microsoft Outlook application. ::: :::Paragraph{listStyleType="disc" indent="2"} **NetBIOS file browsing** - When you select this option, PSAM intercepts NetBIOS name lookups in the TDI drivers on port 137. ::: :::Paragraph{listStyleType="disc" indent="2"} **Citrix** - When you select this option, PSAM intermediates traffic from Citrix applications. ::: The system supports several mechanisms for intermediating traffic to the Lotus Notes, Microsoft Outlook, and Citrix applications. :::Paragraph{listStyleType="disc" indent="2"} **Domain Authentication** - Select this option to allow integrated Windows applications, such as file sharing, Outlook, and so forth to authenticate to the domain controller when the client machine is part of a domain. Before using this option, you must: ::: :::Paragraph{listStyleType="disc" indent="3"} Specify domain controllers that are reachable through the system in the PSAM Destination list so that LDAP and Kerberos traffic can be proxied and sent to the system. ::: :::Paragraph{listStyleType="disc" indent="3"} Configure a PSAM Access Control Policy (ACL) to allow access to all domain controllers. ::: 4. Enter a unique **Name** and optionally a **Description** for the resource profile. 5. Enter the **File Name** and **Path** and in case of **Windows Platform** enter **MD5 Hash**. 6. Under **Autopolicy: SAM Access Control** (this is applicable only for PSAM), click ‘**+**’ specific **Resource** under the Base URL. Enter the full URL of the resource, select **Allow** or **Deny**, and click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/fY3QCB2rJQJQ-_DMz5dj1_cap2576x408.png" alt="img/cap2.png" position="flex-start" size="58" width="576" height="408" initialPath="img/cap2_576x408.png" githubPath="img/cap2_576x408.png" darkWidth="576" darkHeight="408" showCaption="false"} ### Client Applications JSAM JSAM resource profiles configure JSAM to secure traffic to a client/server application. When you create a JSAM application resource profile, the JSAM client tunnels network traffic generated by the specified client applications to servers in your internal network. To create a JSAM applied: 1. Navigate to **Users > Resource Profiles > SAM > Client Applications**. 2. Click ‘**+**’. choose **JSAM** from the Type list. 3. From the Application list, select one of the options. - **Custom** - Select this option to intermediate traffic to a custom application. Then: 1. Under JSAM Port Forwarding click '**+**'. 2. In the **Server Name** field, enter the name or IP address of the remote server. If you are using automatic host mapping, enter the server as it is known to the application. If you enter an IP address, note that end users must connect to JSAM using that IP address in order to connect to the specified server. 3. In the **Server Port** field, enter the port on which the remote server listens for client connections. For example, to forward Telnet traffic from a remote machine, specify port 23 for both the client port (on which JSAM listens) and the server port (on which the Telnet server listens). - To disable the registry change made by JSAM and restore the original copy of the etc/hosts file, users must uninstall the JSAM client using settings in the Preferences > Applications page of the end-user console. To re-enable the change, they need to reboot. - You can also use the restore system settings script. However, the restore system settings script cannot restore the hosts file successfully if you log in as a different user from the one that originally launched JSAM. 4. In the **Client Loopback IP field**, provide a static loopback address. If you do not provide a static IP loopback address, the system assigns an IP loopback address dynamically. 5. In the **Client Port** field, enter the port on which JSAM should listen for client application connections. Typically, the local port value is the same value as the server port; the local port value usually only differs for Linux or Macintosh non-root users who want to add applications for port forwarding that use ports under 1024. 6. Click **Save Changes**. 4. Select the **Allow JSAM to dynamically select an available port if the specified client port is in use** check box if JSAM is listening for multiple hosts on the same port and you want JSAM to select an available port when the client port you specify is taken. The client application must allow you to specify the port number for the connection in order to use this option. 5. Select the **Create an access control policy allowing SAM access to these servers** check box to enable access to the list of servers specified in the Server column (enabled by default). ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/__KoEh980Ot8Dlnx6hc8p_caj1577x528.png" alt="img/caj1.png" position="flex-start" size="58" width="577" height="528" initialPath="img/caj1_577x528.png" githubPath="img/caj1_577x528.png" darkWidth="577" darkHeight="528" showCaption="false"} :::hint{type="info"} For ICS 25.x Gateways, the Lotus Notes and Microsoft Outlook options are deprecated and will be removed in the near future. ::: :::Paragraph{listStyleType="disc" indent="2"} **Lotus Notes** - Select this option to intermediate traffic from the Lotus Notes fat client application. Then, in the Autopolicy: SAM Access Control section, create a policy that allows or denies users access to the Lotus Notes server: ::: :::Paragraph{listStyleType="decimal" indent="3"} If it is not already enabled, select the **Autopolicy: SAM Access Control** check box. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="3"} In the **Resource** field, specify the application server to which this policy applies. You can specify the server as a fully-qualified hostname or an IP/netmask pair. For example, if the fully-qualified hostname is notes1.yourcompany.com, add notes1.yourcompany.com and notes1 to the Resource field. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="3"} From the **Action** list, select **Allow** to enable access to the specified server or **Deny** to block access to the specified server. Click **Save Changes**. You can only use JSAM to configure access to one Lotus Notes application per user role. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/m2al7_Xz2KVsstVmlHLPG_caj2494x460.png" alt="img/caj2.png" position="flex-start" size="49" width="494" height="460" initialPath="img/caj2_494x460.png" githubPath="img/caj2_494x460.png" darkWidth="494" darkHeight="460" showCaption="false" indent="1"} :::Paragraph{listStyleType="disc" indent="2"} **Microsoft Outlook** - Select this option to intermediate traffic from the Microsoft Outlook application. Then: ::: :::Paragraph{listStyleType="decimal" indent="3"} Enter a unique **Name** and optionally a **Description** for the resource profile. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="3"} Enter the **Hostname** for each MS Exchange server in the Servers field. For example, if the fully-qualified hostname is exchange1.yourcompany.com, add exchange1.yourcompany.com to the Servers field. ::: :::Paragraph{listStyleType="disc" indent="4"} You must enter the full name of the servers in this field since the system creates direct one-to-one mappings between the servers you enter here and IP addresses in the etc/hosts file. For more information about registry changes made by JSAM, see the Client-side Changes Guide on the Global Support Center. ::: :::Paragraph{listStyleType="disc" indent="4"} The system does not support Outlook through SVW, since Outlook applications require HKLM registry key changes. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="3"} Select the **Create an access control policy allowing SAM access to these server** check box to enable access to the server specified in the previous step (enabled by default). ::: :::hint{type="info" indent="1"} You can only use JSAM to configure access to one Microsoft Outlook application per user role. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mrabKpRGvcWMP7smIAYWQ_caj3489x340.png" alt="img/caj3.png" position="flex-start" size="49" width="489" height="340" initialPath="img/caj3_489x340.png" githubPath="img/caj3_489x340.png" darkWidth="489" darkHeight="340" showCaption="false" indent="1"} :::Paragraph{listStyleType="disc" indent="2"} **NetBIOS file browsing** - Select this option to tunnel NetBIOS traffic through JSAM. Then: ::: :::Paragraph{listStyleType="decimal" indent="3"} Enter a unique **Name** and optionally a **Description** for the resource profile. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="3"} Enter the fully-qualified **Hostname** for your application servers in the Servers field. ::: :::Paragraph{listStyleType="disc" indent="4"} You must enter the full name of the servers in this field since the system creates direct one-to-one mappings between the servers you enter here and IP addresses in the *etc/hosts* file. For more information about registry changes made by JSAM, see the Client-side Changes Guide on the Global Support Center. ::: :::Paragraph{listStyleType="disc" indent="4"} If you want to enable drive mapping on a Windows client machine, use the standard NetBIOS file browsing option. When you do, JSAM automatically modifies the registry to disable port 445 on Windows machines, which forces Windows to use port 137, 138, or 139 for drive-mapping. Windows users need to reboot one time to enable the registry change to take effect. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="3"} Select the **Create an access control policy allowing SAM access to these server** check box to enable access to the server specified in the previous step (enabled by default). ::: :::hint{type="info" indent="1"} You can only use JSAM to configure NetBIOS file browsing once per user role. ::: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/EkQaccvoJs7m0KI5WVBag_caj4487x325.png" alt="img/caj4.png" position="flex-start" size="49" width="487" height="325" initialPath="img/caj4_487x325.png" githubPath="img/caj4_487x325.png" darkWidth="487" darkHeight="325" showCaption="false" indent="1"} 6. Click **Save Changes**. ### PSAM Destinations When you create a PSAM destination network resource profile, the PSAM client intercepts requests from processes running on the client to internal hosts. When destinations (using either IP address or hostnames) are configured on the system, all DNS and NetBIOS names are resolved through the system. To create a PSAM destination network resource profile: 1. Navigate to **Users > Resource Profiles > SAM > PSAM Destinations**. 2. Click ‘**+**’, enter a unique **Name** and optionally a **Description** for the resource profile. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/n5z_T_68mUofsoO5ZS_ud_psam1528x116.png" alt="img/psam1.png" position="flex-start" size="53" width="528" height="116" initialPath="img/psam1_528x116.png" githubPath="img/psam1_528x116.png" darkWidth="528" darkHeight="116" showCaption="false" indent="1"} 3. In the PSAM Destinations section, click ‘**+**’, specify which servers you want to secure using PSAM. You can specify the servers as hostname or IP/netmask pairs. You may also include a port. and click **Save Changes**. 4. Select the **Create an access control policy allowing SAM access to this server** check box to enable access to the server specified in the previous step (enabled by default). 5. Click **Save Changes**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/_LKP317gWCZv8qDKughuJ_psam2611x363.png" alt="img/psam2.png" position="flex-start" size="61" width="611" height="363" initialPath="img/psam2_611x363.png" githubPath="img/psam2_611x363.png" darkWidth="611" darkHeight="363" showCaption="false"} ### Secure Mail To use Secure Mail for iOS devices, you must enable it at the role level and then create a resource profile that specifies the Exchange server and encryption settings. You must also obtain and import an S/MIME certificate. To define the Secure Mail resource profile: 1. Navigate to **Users > Resource Profiles > Mobile**. 2. Specify the information in the following table: ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/quKAOG2NPItxcmUQLB01U_secure581x530.png" alt="img/secure.png" position="flex-start" size="58" width="581" height="530" initialPath="img/secure_581x530.png" githubPath="img/secure_581x530.png" darkWidth="581" darkHeight="530" showCaption="false"} | Setting | Guidelines | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Virtual Hostname | Enter a hostname alias for the Exchange server, and update your DNS server to map the alias to the IP address of Ivanti Connect Secure. The name must be unique among all virtual hostnames.
For example, if the virtual hostname is email.com, and the backend URL is https\://mail.pulsesecure.net:8080, a client request to https\://email.com/test1 via Ivanti Connect Secure is converted to https\://mail.pulsesecure.net:8080/test1. The response to the converted request is sent to the client web browser. | | Exchange Server | Enter the URL and port number of the Microsoft Exchange server, such as https\://mail.pulsesecure.net:379. If the port number is omitted, it defaults to 80. | | Description | Description of the Exchange server (optional). | | Username | Select one of the following to specify the e-mail account format used by the Exchange server:
- **None**: Inserts the \ variable for the user's login name for Ivanti Connect Secure (the default).
- **Exchange 2007/2010/2013**: Inserts the \\ variables to include the user's domain before the login name.
- **Office 365**: Inserts \@domain.com, and you can enter the appropriate domain, such as \@pulsesecure.net. | | Secure Mail Options | Select one or more of the following encryption options:
- **Encrypt Body**: Encrypts the body of the e-mail using an S/MIME certificate. The encrypted e-mail body can be viewed by any native e-mail client.
- **Encrypt Attachments**: Encrypts the e-mail attachments using a key generated by Ivanti Connect Secure. Encrypted attachments, which must be opened with Ivanti Mobile Client, are identified by a pulsesecure file extension, such as report.pdf. pulsesecure. The encrypted file types are listed in the File Extensions text box, separated by semicolons. You can add or delete file extensions from the list.
- **Allow Outbound E-Mail Attachments**: Decrypts attachments before forwarding an e-mail to an external account. If this option is not selected, e-mails are forwarded without attachments and include a note indicating that attachments were removed. | :::Paragraph{indent="1"} Graphics embedded in the encrypted e-mail body are displayed twice on iOS devices. ::: :::Paragraph{indent="1"} If you add .gif, .jpeg, .jpg, .png or .htm to the list of encrypted file types, graphics embedded in the e-mail body are not displayed correctly on iOS devices. ::: :::Paragraph{indent="1"} If you change the encryption settings, onboarded devices must be re-onboarded to obtain the new settings. ::: 3. Click **Save Changes**. ### S/MIME Certificate If you enable Secure Mail, an S/MIME is required for each client device. You can generate an S/MIME certificate for each device or use a global certificate for all devices by requesting an S/MIME certificate from a Certificate Authority (CA) and importing the certificate and private key to Ivanti Connect Secure. To generate or import an S/MIME certificate: 1. Navigate to **Users > Resource Profiles > Mobile > S/MIME Certificate**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/TUVLUjqlewsXoGhOnkEY0_smime1573x225.png" alt="img/smime1.png" position="flex-start" size="57" width="573" height="225" initialPath="img/smime1_573x225.png" githubPath="img/smime1_573x225.png" darkWidth="573" darkHeight="225" showCaption="false"} 2. Specify one of the following options: | Setting | Guidelines | | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Generate per User Certificate** | Select this option to use the SCEP server and a CSR template to generate a certificate for each client. Select a CSR template from the Use Certificate Template list. To create a CSR template, see Configuring Enterprise Onboarding. | | Upload and Use Single Global Certificate | Select this option to use the same certificate for all client devices. Click **Import Certificate & Key**, click **file** field in one of the following forms to locate the **certificate file**, enter the **password key** if the file is encrypted, and then click **Import**.
- **If certificate file includes private key**: When the certificate and key are contained in one file.
- **If certificate and private key are separate files**: When the certificate and key are in separate files.
- **Import via System Configuration file**: When the certificate and key are contained in a system configuration file that has been exported from Ivanti Connect Secure. | ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/mGMwozyl29bQhVlawR7r5_smime2346x554.png" alt="img/smime2.png" position="flex-start" size="35" width="346" height="554" initialPath="img/smime2_346x554.png" githubPath="img/smime2_346x554.png" darkWidth="346" darkHeight="554" showCaption="false"} ## Resource Policies A resource policy is a system rule that specifies resources and actions for a particular access feature. A resource is either a server or file that can be accessed through the system, and an action is to "allow" or "deny" a resource or to perform or not perform a function. Each access feature has one or more types of policies, which determine the system's response to a user request or how to enable an access feature. You may also define detailed rules for a resource policy, which enable you to evaluate additional requirements for specific user requests. You can create the following types of resource policies through the Resource Policies pages: - **Web Resource Policies** - specify the Web resources to which users may or may not browse. They also contain additional specifications such as header caching requirements, servers to which java applets can connect, code-signing certificates that the system should use to sign java applets, resources that the system should and should not rewrite, applications for which the system performs minimal intermediation, and single sign-on options. - **File Resource Policies** - specify the Windows, UNIX, and NFS file resources to which users may or may not browse. hey also contain additional specifications such as file resources for which users need to provide additional credentials. - **Secure Application Manager Resource Policies** - allow or deny access to applications configured to use JSAM or PSAM to make socket connections. - **Terminal Services Policies** - allow or deny access to the specified Windows servers or Citrix Metaframe servers. - **VPN Tunneling Resource Policies** - allow or deny access to the specified servers and specified IP address pools. - **HTML5 Access Resource Policies** - allow or deny clientless to terminal servers using RDP/SSH/Telnet protocols. :::hint{type="info"} You can also create resource policies as part of the resource profile configuration process. In this case, the resource policies are called "advanced policies." ::: Resource policies are an integral part of the access management framework, and therefore are available on all Ivanti Connect Secure products. However, you can access only resource policy types that correspond to your licensed features. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/msUd7fz7-tDzX48pUPbWf_respol602x343.png" alt="img/respol.png" position="flex-start" size="60" width="602" height="343" initialPath="img/respol_602x343.png" githubPath="img/respol_602x343.png" darkWidth="602" darkHeight="343" showCaption="false"} ### Proxy Servers for PSAM Connection ICS Gateway supports Proxy Server for connections to PSAM destination (TCP only) via Proxy Servers. Administrators can modify existing policies to route traffic through proxy servers, enhancing both security and scalability. To specify the SAM resource option: 1. From the Gateways List page, select **\ > Users > Resource Policies > SAM > Proxy Server**. 2. Click the Add icon and then enter **Host address** and **Port number**. Click **Save Changes** to use the proxy servers and allow web traffic to bypass direct connection. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/tu8x7wPoltofgh_t10jS5_psamproxy214x197.png" position="flex-start" size="21" width="214" height="197" initialPath="img/psam_proxy_214x197.png" githubPath="img/psam_proxy_214x197.png" darkWidth="214" darkHeight="197" showCaption="false"} 3. Within your SAM policy, you now have an additional option under Actions to allow socket access via the proxy server. Select **Resource Policy > SAM > (Policy Name)**, and from the **Actions** drop-down list, select **Allow Socket Access Via Proxy Server.** 4. You may also set proxy server usage within Detailed Rules for more granular control. Select **Resource Policy > SAM > (Policy Name) > Detailed Rules**, and select **Allow socket access.** ### Creating VPN Tunneling Connection Profiles Use the **VPN Tunneling > Connection Profiles **page to create VPN tunneling connection profiles. When the system receives a client request to start a VPN tunneling session, it assigns an IP address to the client-side agent. The system assigns this IP address based on the DHCP Server or IP Address Pool policies that apply to a user's role. In addition, this feature allows you to specify the transport protocol, encryption method, and whether or not to employ data compression for the VPN tunneling session. Nodes in a multi-site cluster share configuration information, which means that devices in different networks share an IP address pool. Since any node may receive the client request to start the VPN tunneling session, you need to specify an IP filter for that node that filters out only those network addresses available to that node. When the cluster node receives a request to create a VPN tunnel, it assigns the IP address for the session from the filtered IP address pool. :::hint{type="info"} Ivanti recommends using standalone nodes or clusters of a maximum of two nodes behind a load balancer. ::: :::hint{type="info"} Ivanti Security Appliance (ISA)/ISA-V does not support clusters containing more than two nodes for ICS. ::: To write a **VPN tunneling connection profile**: 1. From the Gateways List page, select **\ > Users > Resource Policies > VPN Tunneling > Connection Profiles**. 2. On the **Connection Profiles** page, click A and configure the settings described in the following table. 3. **Save** the configuration. 4. On the **Connection Profiles** page, order the profiles according to how you want to evaluate them. Keep in mind that once the system matches the resource requested by the user to a resource in a profile's (or a detailed rule's) Resource list, it performs the specified action and stops processing profiles. See the following table. **VPN Tunneling Connection Profile Settings** | Setting | Guidelines | | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | A name to label this policy. | | Description | A description of the policy (optional). | | **IPv4 address assignment** | | | Enable IPv4 address assignment to clients | Select this option to enable IPv4 connections and to specify how IPv4 addresses are assigned to clients.
**IPv6-only** address assignment is supported on ISAC Windows Desktop, but not on MacOS, Linux, or mobile platforms (iOS and Android). | | DHCP servers | Specify the hostname or IP address of a network Dynamic Host Configuration Protocol (DHCP) server responsible for handling client-side IP address assignment.
You can specify up to three DHCP servers by listing each one on a separate line. When multiple DHCP servers are listed, the system sends a DHCP Discover message to all listed DHCP servers and then waits five seconds for a response. If multiple DHCP servers respond, the system chooses the one with the longest lease period.
The system sends a DHCP release packet to the DHCP server when the VPN tunneling session ends.
DHCP provides a framework for passing configuration information to hosts. Configuration parameters and other control information are carried in tagged data items that are stored in the options field of the DHCP message. You can specify the DHCP options to forward by entering the option number, its value and type and then clicking Add. For a complete list of DHCP options, see the "RFC2132 - DHCP Options and BOOTP Vendor Extensions" article available on the Internet. To delete an option, select the check box next to the option number then click the Delete button. | | DHCP options | By default, the client's hostname is sent by Ivanti Connect Secure to the DHCP server in the DHCP hostname option. Passing the useruid in the DHCP hostname option is no longer supported. As an alternative, you can configure the following entry in the DHCP options table. Admins can configure any sub-option (1-255) for DHCP option. DHCP option 82, sub-option 5 is qualified and other options are compatible.
For example:
option number=12, option value=\\, option type=String
Or you can pass a value by adding an entry in the DHCP options table for hostname with whatever value you want. For example:
option number=12, option value=foo, option type=String | | IPv4 address pool | Specify IP addresses or a range of IP addresses for the system to assign to clients that run the VPN tunneling service. Use the canonical format: ip\_range.
The last component of the IP address is a range delimited by a hyphen (-). No special characters are allowed. The ip\_range can be specified as shown in the following list:
a.b.c.d - Specifies a single IP address.
a.b.c.d-e.f.g.h - Specifies all IP addresses from the first address to the last address, inclusive.
a.b.c.d-f.g.h - An abbreviated form that specifies the range a.b.c.d through a.f.g.h
a.b.c.d-g.h - An abbreviated form that specifies the range a.b.c.d through a.b.g.h.
a.b.c.d-h - An abbreviated form that specifies the range a.b.c.d through a.b.c.h.
a.b.c.d/mask - Follows CIDR notation to assign the IPv4 address.
For example , 172.21.10.10/31 will not assign any IP address to the ISAC client , with /31 we get only two addresses
172.21.10.10 - network address cannot be assigned to the ISAC client.
172.21.10.11 - Broadcast address cannot be assigned to the ISAC client.
In case of CIDR we need to have address space of minimum 4 addresses , so that two addresses are used for network and broadcast respectively and we will have two addresses to assign to the Host/ISAC client.
Be sure to specify a sufficient number of addresses in the IP address pool for all of the endpoints in your deployment. When all of the addresses in the pool have been assigned to endpoints, additional endpoints are unable to obtain a virtual IP address and are blocked from accessing protected resources. The system logs a message in the Event log when an IP address cannot be assigned to an endpoint.
We recommend that you set up your network so that the client-side IP address pool, or the DHCP server specified in the VPN tunneling connection profile, resides on the same subnet as Ivanti Connect Secure.
If your network topology dictates that the system internal IP interface and the IP address pool or DHCP server reside on different subnets, you need to add static routes to your intranet's gateway router(s) to ensure that your Enterprise resources and Ivanti Connect Secure can see each other on the internal network.
If you are running a multi-unit cluster across a LAN, make sure that the IP address pool contains addresses that are valid for each node in the cluster. Then, configure an IP filter for each node to apply to this IP address pool.
The system does not support a common IP address pool for VPN tunneling for an Active/Active cluster. In A/A VPN tunneling deployments, we recommend that you split the IP pool into node-specific sub-pools. Furthermore, you are advised to perform static route configuration on the backend router infrastructure in a coordinated fashion, with static routes to each sub-pool pointing to the internal IP address of the hosting cluster node as the next-hop gateway.
IP address pool also supports attribute substitution. For example, you can enter a RADIUS role mapping attribute in this field, such as \. | | **IPv6 address assignment** | | | Enable IPv6 address assignment to clients | Select this option to enable IPv6 connections.
IPv6 must be enabled on internal interface for IPv6 addresses to be allocated to clients. | | DHCPv6 servers | Specify the hostname or IPv6 address of a network Dynamic Host Configuration Protocol (DHCP) server responsible for handling client-side IP address assignment.
You can specify up to three DHCP servers by listing each one on a separate line. When multiple DHCP servers are listed, the system sends a DHCP Discover message to all listed DHCP servers and then waits five seconds for a response. If multiple DHCP servers respond, the system chooses the one with the longest lease period.
The system sends a DHCP release packet to the DHCP server when the VPN tunneling session ends.
This feature is available on 22.5R2.1 release. | | DHCP Subnet Selection | This option allows ICS to specify the subnet on which to allocate an IP address. Specify the IPv6 prefix address, which defines the range of IPaddress to be assigned by the DHCP server for the Profile users. For example: f00:112\::/64
This feature is available on 22.5R1/22.6R2 release. | | IPv6 address pool | Specify IPv6 address ranges for this profile, one per line. Like the IPv4 address pool, the configuration supports entering ip\_range values. We recommend using the IPv6 network prefix / netmask style (such as 2001\:DB8\::6:0/112). | | **Connection settings** | | | Transport | Select one of the following options for transport, encryption, and compression settings:
**ESP **- Use a UDP encapsulated ESP transfer method to securely transfer data between the client and Connect Secure. ESP uses an LZO compression algorithm. You can use the default settings or configure data transfer parameters by defining the UDP port, ESP-to-SSL fallback time-out value, and ESP encryption key lifetime values.
**SSL** - Use the standard SSL transport method. SSL uses a deflate compression method. In SSL mode, compression is controlled by the Enable GZIP compression option on the System Maintenance Options page.
To support IPv6 connections, be sure to set MTU greater than 1380. We recommend 1500. If the MTU value on the external interface is lower than 1380 and IPv6 address assignment is enabled, the transport setting for the connection profile is ignored. To avoid IP fragmentation, the session falls back to SSL mode for both IPv6 and IPv4 traffic. | | | If you select ESP mode, configure the following transport and compression settings:
**UDP port - **Port through which you intend to direct UDP connection traffic. The default port number is 4500.
Whether you specify a custom port number or choose to use the default port number (4500), you must also ensure that other devices along the encrypted tunnel allow UDP traffic to pass between Ivanti Connect Secure and the clients. For example, if you employ an edge router and a firewall between the Internet and your corporate intranet, you must ensure that port 4500 is enabled on both the router and the firewall and that port 4500 is configured to pass UDP traffic.
IKEv2 uses port 500 exclusively. Do not configure port 500 in your VPN Tunneling profiles.
**ESP to SSL fallback timeout - **Period of time (in seconds) to fall back to the SSL connection already established following UDP connection failure. The default is 15 seconds.
A nonconfigurable idle timeout of 60 seconds also affects when fallback occurs. After the tunnel is established through ESP, the client sends keepalives after 60 seconds of inactivity on the ESP channel (the idle timeout). The total time to fallback is therefore the idle timeout (60 seconds) plus the fallback timeout. For example, if ESP to SSL fallback timeout is set to 25 seconds, it takes approximately 60+25 or 85 seconds for the VPN tunneling client to switch.
**Key lifetime (time based)** - Period of time (in minutes) the system continues to employ the same ESP encryption key for this connection profile. Both the local and remote sides of the encrypted transmission tunnel use the same encryption key only for a limited period of time to help prevent unauthorized access. The default is 20 minutes.
**Key lifetime (bytes transferred) **- Maximum amount of data that is transferred on the tunnel for an ESP encryption key. The default is 0 bytes, meaning no limit.
When either of the key lifetime limits is reached, a new key is exchanged between Connect Secure and the client. The reason for changing keys is to help prevent unauthorized access, however, changing the encryption key too frequently can increase CPU overhead on the system. | | | **Replay Protection** - Activates replay protection. When enabled, this option protects against hostile "repeat attacks" from the network. When packets arrive from the client, the system checks the IP header information to verify that a packet featuring the same IP header information has not already been received. If one has been received, the packet is rejected. This option is enabled by default.
If you activate the Enable TOS Bits Copy option, IP packets with different TOS bits may be reordered when passing through gateway routers on your network. To ensure that any packets received out of order are not automatically dropped when they reach the system, you can disable the Replay Protection option.
We recommend that you leave replay protection enabled if you are not expecting more than one source of packets from the client (for example, if only one application is transmitting and receiving traffic over the VPN tunnel).
**PQC Mode** - Enables or disables Post-Quantum Cryptography (PQC). When enabled, only **AES256/SHA256** or** AES256/GCM16** encryption can be used. If **AES256/GCM16** is not supported, the system automatically falls back to **AES256/SHA256**.
**Compression** - Use compression for the secure connection. Compression is useful for a slow link but may cause issues in extremely large deployments since extra cycles are spent compressing the data.
If you have selected ESP, select one the following encryption settings:
**AES128/MD5 (maximize performance)** - Uses Advanced Encryption Standard (AES) 128-bit encryption on the data channel and the MD5 authentication method for VPN tunneling sessions.
**AES128/SHA1** - Uses AES 128-bit encryption on the data channel and the SHA1 authentication method during VPN tunneling sessions.
**AES256/MD5** - Uses AES 256-bit encryption on the data channel and the MD5 authentication method for VPN tunneling sessions.
**AES256/SHA1 (maximize security) **- Uses AES 256-bit encryption on the data channel and the SHA1 authentication method during VPN tunneling sessions.
**AES256/SHA256 (maximize security)** - Uses AES 256-bit encryption on the data channel and the SHA2 authentication method during VPN tunneling sessions.
The MD5 authentication algorithm creates digital signatures. The MD5 authentication method translates an input string (like a user's ID or sign-in password, for example) into a fixed, 128-bit fingerprint (also called a "message digest") before it is transmitted to or from the system. | | **DNS settings** | | | IVE DNS Settings | In the DNS Settings section, select an option that determines the settings sent to the client:
**IVE DNS Settings** - Send the system DNS settings.
**Manual DNS Settings** - Override standard DNS settings with the settings you provide:
**Primary DNS** - Enter the IP address for the primary DNS.
**Secondary DNS** - Enter the IP address for the secondary DNS.
**DNS Domain(s)** - Enter the DNS domain(s), such as "yourcompany.com, yourcompany.net".
**WINS**-Enter the WINS resolution name or IP address.
**DHCP DNS Settings** - Send to the client the values the DHCP server sends to Ivanti Connect Secure. There is no fallback to the DNS settings if the DHCP Server does not send any values. | | Auto-allow | Select **Auto-allow IP's in DNS/WINS settings (only for split-tunnel enabled mode) **if you want to create an allow rule for the DNS server. For example, if you have defined policies to allow requests from IP address 10.0.0.0 but your DNS server has an address of 172.125.125.125 the DNS server requests will be dropped. If you select this option, the system creates a rule to allow the DNS requests. | | **Release Prior to 25.1.3.0 use **DNS search order | Select the DNS server search order. Applicable only if split tunneling is enabled:
- Search client DNS first, then the device
- Search the device's DNS servers first, then the client
- Search device DNS only.
DNS search order does not work with iOS clients. The DNS name resolution fields (located on the System > Network > Overview window) must be configured, otherwise all DNS queries will go to the client's DNS server.
"Search device DNS only" is not supported for IPv6 DNS.
Ivanti Secure Access Client and greater supports all DNS search order options. Prior versions of Ivanti Secure Access Client support only Search client DNS first, then the device and Search the device's DNS servers first, then the client.
For the Search client DNS first, then the device and Search the device's DNS servers first, then the client options, DNS configured on the system are added to the end user's system along with the existing DNS already available on the end user's system. So, either the device DNS servers or client DNS servers get precedence at the end user's systems.
When the Search device DNS only option is selected, DNS on the end user's system are replaced with device DNS. This option is recommended to avoid ISP's DNS hijacking. Note that this option is applicable only for Windows platforms; non-Windows clients will use the Search the device's DNS servers first, then the client search order if this option is selected. When using this option, you must ensure that packets to the system DNS are going through the tunnel. To do this, add the required routes to the split tunnel networks policy (Users > Resource Policies > VPN Tunneling > Split-Tunneling Networks), or select the Auto-allow IPs in DNS/WINS settings option.
For the Search device DNS only option, the client software, removes the DNS information of the available adapters on the client system after the tunnel is created. Once the tunnel is created, the client does not monitor the presence of new adapters and does not monitor if changes are made to the DNS settings of existing adapters. Because of this, the Search device DNS only option may not work properly if any of the following occurs after the tunnel is created:
A new interface appears with a DNS server that does DNS hijacking.
A third-party application adds DNS to the adapters whose DNS was removed by the client as part of the tunnel set up process.
Third-party applications change the TCP/IP option from "Use the following DNS servers" to "Obtain DNS servers automatically" for those adapters whose DNS was removed by the client software as part of the tunnel set up process.
End users enable the interfaces that are in the disabled state during the tunnel set up process.
On Windows 8, selecting either the first or second radio button sends DNS requests to both the client's and gateway's DNS at the same time. On Windows 10, selecting the first radio button will have the same effect as the second button. | | **From Release 25.1.3.0 use **Split DNS Settings | **Tunnel All DNS queries**: If selected then, in this scenario, regardless of the configuration whether IP-based split tunneling rules only, FQDN-based split tunneling rules only, or a combination of both, all DNS queries are tunneled.
**Split DNS**: Select any one of the following:
- DNS queries not matching the include and exclude FQDNs are sent through physical adapter.
OR
- DNS queries not matching the include and exclude FQDNs are tunneled through ICS.
**IP based split tunneling rules only**: The DNS query is tunneled when the query FQDN matches the configured DNS suffixes or search domains. Otherwise, the query is not tunneled.
**FQDN based split tunneling rules only**: A DNS query is tunneled if its FQDN matches an included FQDN or domain, or if it does not match any configured include or exclude entries. If the FQDN matches an excluded FQDN or domain, the query is not tunneled.

**Notes**:
- DNS queries matching the include FQDNs or DNS suffixes are tunneled; DNS queries that match the exclude FQDNs are sent through the physical adapter.
- Split DNS is supported only on Windows clients. macOS and Linux clients do not support split DNS and will always work on the "Tunnel All DNS queries" mode. | | **Proxy Server Settings** | | | Proxy server settings | Select one of the following options: | | | **No proxy server - **Specifies that the new profile requires no proxy server.
**Automatic (URL for PAC file on another server) - **Specify the URL of the server on which the PAC file resides, and the frequency (in minutes) with which the client polls the server for an updated version of the PAC file. You can configure VPN tunneling to check for an updated PAC files as often as every 10 minutes. The default (and minimum) update period is 10 minutes. The PAC file should reside on a Web server, not on the local PC.
The PAC file update method runs on a 10-minute interval. Specifying a frequency update period that is a multiple of 10 will get an exact result. If you specify the update frequency at a value that is not a multiple of 10, it is rounded up to the next interval. For example, if you specify the update frequency at 15 minutes, the system updates a PAC file every 20 minutes.
VPN tunneling limits the size of internal (server side) PAC files. The logical maximum size is 256 KB. The actual maximum size that can be used in your deployment might be smaller, reduced according to the size of other VPN tunneling settings in use, such as the number of split tunnel networks and DNS suffix entries.
**Manual configuration **- Specify the IP address or the hostname of the server and provide the port assignment.
**Preserve client-side proxy settings - **By default, VPN tunneling may change proxy settings when needed. For example, VPN tunneling may temporarily change the proxy settings of the browser so that traffic intended for the VPN session uses the temporary proxy settings. Select the Preserve client-side proxy settings option to prevent the client-side proxy settings from being overridden by VPN tunneling.
If you select this option, HTTP and FTP traffic path can change after VPN tunneling establishing the connection. Please analyze the proxy logic and split-tunnel option, and make sure it directs the traffic as intended.
**Disable client-side proxy settings - **Disables the client's proxy settings after the VPN tunnel is established.
In the use case where the client proxy configuration (proxy.pac) is hosted on a LAN server and users are outside the office network, proxy.pac is not accessible and users access the Internet directly. However, after a VPN tunnel is established, proxy.pac becomes accessible, and that causes all Internet requests to go through the tunnel to the proxy server. When you select Disable client-side proxy settings, client requests are served through the Ivanti server directly. When the tunnel is disconnected, the client proxy settings are restored. | | Roles | Specify one of the following options:
**Policy applies to ALL roles **- To apply this policy to all users.
**Policy applies to SELECTED roles **- To apply this policy only to users who are mapped to roles in the Selected roles list. Make sure to add roles to this list from the Available roles list.
**Policy applies to all roles OTHER THAN those selected below - **To apply this policy to all users except for those who map to the roles in the Selected roles list. Make sure to add roles to this list from the Available roles list. | ### VPN Tunneling Resource Policy Configuration Use Case This topic describes a real-world VPN tunneling application and the steps necessary to configure the appropriate resource policy providing access to remote users on the network. Large financial institutions (also called Fortune Companies) require a robust client sign-in application like VPN tunneling to help provide remote employees seamless network connection to a large range of enterprise resources at the corporate headquarters. Often, remote users need to be able to access multiple applications on their laptops/client machines beyond simple e-mail or meeting scheduling applications. These remote super users or power users require secure, encrypted access to powerful server applications like Microsoft OutlookTM, OracleTM databases, and the RemedyTM case management system. :::hint{type="info"} \- FQDN supports IPv6 only on Windows, and IPv4 only on other platforms. \- FQDN-based split tunneling supports dual stack (both IPv6 and IPv4) only on Windows, and not supported on other platforms. \- FQDN based split tunneling only supported with IPv4 Traffic Enforcement feature enabled for the respective role. ::: For this scenario, let's assume the following: - There is a small collection of remote users who will all access their financial institution's enterprise resources via the same device. - All the users have the same user\_role\_remote role assigned to their user ID - Host Checker and Cache Cleaner are configured and verifying the users' machines upon logging into a device and launching their VPN tunneling sessions - All users require access to three large servers at the corporate headquarters with the following attributes: - `outlook.acme.com` at IP address 10.2.3.201 - `oracle.financial.acme.com` at IP address 10.2.3.202 - `case.remedy.acme.com` at IP address 10.2.3.99 - Because the Company wants to manage their IP address pool very strictly, each device provides IP addresses to remote users (our particular device controls the IP addresses between 10.2.3.128 and 10.2.3.192) - The company is interested in the most secure access possible, simultaneously accepting only the least possible amount of client down-time To configure a VPN tunneling resource policy providing appropriate access to the Fortune Company remote users: 1. Create a new **VPN tunneling resource policy** where you specify the three servers to which you want to grant remote users access: - In the **New Profile**section, specify the IP address ranges necessary to allow access to the three servers (**outlook.acme.com**, **oracle.financial.acme.com**, and **case.remedy.acme.com**) separated by carriage returns. ```bash udp://10.2.3.64-127:80,443 udp://10.2.3.192-255:80,443 ``` :::hint{type="info"} Configuring your resource as 10.1.1.1-128:\* is not supported. Doing so will result in an error. ::: - In the **Roles **section, select the **Policy applies** to **SELECTED** roles option and ensure that only the "user\_role\_remote" role appears in the **Selected roles** list. - In the Action section, select the **Allow access** option. 2. Create a new VPN tunneling connection profile where you define the transport and encryption method for the data tunnel between the client(s) and system: - In the** IP address assignment **section, select the disable IPv4 address assignment and enable IPv6 address assignment check boxes as per your requirement. Then specify the assignable IPv4 address and IPv6 address ranges in the associated text field. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/o7GpMcy1kqRQAoEm9M8Tv_vpntunnelconfig680x623.png" position="flex-start" size="68" width="680" height="623" initialPath="img/vpn_tunnel_config_680x623.png" githubPath="img/vpn_tunnel_config_680x623.png" darkWidth="680" darkHeight="623" showCaption="false"} - In the **Connection Settings **section, select the **ESP transport **option and the **AES/SHA1 encryption** option. - In the **Roles** section, select the **Policy applies** to **SELECTED** roles option and ensure that only the "user\_role\_remote" role appears in the **Selected roles** list. ## Ivanti Secure Access Client Connections An Ivanti Secure Access component set includes specific software components that provide Ivanti Secure Access Client connectivity and services. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/dAo64UZLoSLt79i6PHUNe_pscliconnections615x250.png" alt="img/ps_cli_connections.png" position="flex-start" size="62" width="615" height="250" initialPath="img/ps_cli_connections_615x250.png" githubPath="img/ps_cli_connections_615x250.png" darkWidth="615" darkHeight="250" showCaption="false"} ### Ivanti Secure Access Client Connection Set Options The following items apply to all connections in a connection set. - Allow saving logon information: Controls whether the Save Settings check box is available in login dialog boxes in Ivanti Secure Access Client. If you clear this check box, Ivanti Secure Access Client always requires users to provide credentials. If you select this check box, users have the option of saving their credentials. - Ivanti Secure Access Client can retain learned user settings: These settings are retained securely on the endpoint, evolving as the user connects through different Ivanti servers. Ivanti Secure Access Client can save the following settings: - Certificate acceptance - Certificate selection - Realm - Username and password - Proxy username and password - Secondary username and password - Role - **VPN only access:** When Ivanti Secure Access Client connects to Ivanti Connect Secure having lock down mode enabled, it will enable lock-down mode and block network if VPN is not in connected state. When VPN only access option is enabled, the Enable captive portal detection and Enable embedded browser for captive portal will be automatically checked and cannot be edited. - **Display splash screen:** Clear this check box to hide the Ivanti Secure Access Client splash screen that normally appears when Ivanti Secure Access Client starts. - **Dynamic certificate trust:** Determines whether users can opt to trust unknown certificates. If you select this check box, a user can ignore warnings about invalid certificates and connect to the target Ivanti server. This feature is disabled by default. :::hint{type="info"} By default, Dynamic certificate trust check box will be unchecked. ::: - **Dynamic connections:** Allows connections within this connection set to be automatically updated or added to Ivanti Secure Access Client when the user connects to Ivanti Connect Secure through the user Web portal, and then starts Ivanti Secure Access Client through the Web portal interface. Dynamic connections are created as manual rather than automatic connections, which means that they are run only when the user initiates the connection or the user browses to a Ivanti server and launches Ivanti Secure Access Client from the server’s Web interface. If dynamic connections are disabled, and the user logs in through the Web portal of a Ivanti server that is not already included in Ivanti Secure Access Client’s connection set, then starting Ivanti Secure Access Client from the Web portal does not add a new Ivanti Secure Access Client connection for that Ivanti server. If you choose to disable dynamic connections, you can still allow users to manually create connections by enabling Allow User Connections. - **Enable captive portal detection:** To detect the presence of a captive portal hotspot enable this option. It can be applied only to Ivanti Connect Secure and Ivanti Policy Secure (L3) connections. - **Enable embedded browser for captive portal:** When enabled, Ivanti Secure Access Client uses an embedded web browser that the end user can use to traverse captive portal pages and to gain network connectivity for establishing a VPN connection. This applies only when captive portal detection is enabled. - **Enable embedded browser for authentication:** When enabled, Ivanti Secure Access Client uses embedded browser for SAML, Custom Sign-in or token-based authentication, rather than external browser. This feature is supported only on Windows. - **FIPS mode enabled:** Enable FIPS mode communications for all Ivanti Secure Access Client connections in the connection set. The Federal Information Processing Standard (FIPS) defines secure communications for the U.S. government. When a Ivanti Secure Access Client connection is operating in FIPS mode, FIPS On appears in the lower corner of the Ivanti Secure Access Client interface. If your Ivanti Connect Secure hardware does not support FIPS mode operations, FIPS mode configuration options are not present in the admin console interface. FIPS mode operations are supported on ISA-V Series Ivanti Gateways and a few ISA series appliances. :::hint{type="info"} Users cannot enable FIPS mode from within Ivanti Secure Access Client. You must create FIPS-enabled connections on the server and deploy them. ::: - **Prevent caching smart card PIN:** Enabling this field will allow system administrators to prevent smart card PIN values from being cached. This feature is applicable only to Windows. - **Wireless suppression:** Disables wireless access when a wired connection is available. If the wired connection is removed, Ivanti Secure Access Client enables the wireless connections with the following properties: - Connect even if the network is not broadcasting. - Authenticate as computer when computer information is available. - Connect when this network is in range. :::hint{type="info"} Wireless suppression occurs only when the wired connection is connected and authorized. If you enable wireless suppression, be sure to also configure a connection that enables Ivanti Secure Access Client to connect through a wired connection. ::: ### Creating a Client Connection Set for Ivanti Connect Secure To create a Ivanti Secure Access Client connection set: 1. Select **Users > Ivanti Secure Access Client > Connections**. 2. Click '+' to create a new connection set. 3. Enter a name and, optionally, a description for this connection set. 4. Under Options, select or clear the following check boxes: - **Allow saving logon information**: Controls whether the Save Settings check box is available in login credential dialog boxes in Ivanti Secure Access Client. If you clear this check box, Ivanti Secure Access Client always requires users to provide credentials. If you select this check box, users have the option of saving their credentials. - **Allow user connections**: Controls whether connections can be added by the user through the Ivanti Secure Access Client interface. - **Always-on Ivanti Secure Access Client**: Prevent end users from circumventing Ivanti Secure Access Client connections. This option disables all configuration settings that allow the end user to disable or remove Ivanti Secure Access Client connections, service or software. - **VPN only access**: When Ivanti Secure Access Client connects to Ivanti Connect Secure having lock down mode enabled, it will enable lock-down mode and block network if VPN is not in connected state. - **Display splash screen**: Clear this check box to hide the Ivanti Secure Access Client splash screen that normally appears when Ivanti Secure Access Client starts. - **Dynamic certificate trust**: Determines whether users can opt to trust unknown certificates. If you select this check box, a user can ignore warnings about invalid certificates and connect to the target Ivanti server. This feature is disabled by default. - **Dynamic connections**: Allows new connections to be added automatically to Ivanti Secure Access Client when the user logs into a Ivanti server through the server’s Web portal, and then starts Ivanti Secure Access Client though the Web portal interface. - **FIPS mode enabled**: Enable FIPS mode communications for all Ivanti Secure Access Client connections in the connection set. The Federal Information Processing Standard (FIPS) defines secure communications for the U.S. government. When a Ivanti Secure Access Client connection is operating in FIPS mode, FIPS On appears in the lower corner of the Ivanti Secure Access Client interface. - **Wireless suppression**: Disables wireless access when a wired connection is available. Wireless suppression occurs only when the wired connection is connected and authorized. - **Prevent caching smart card PIN**: Enabling this field will allow system administrators to prevent smart card PIN values from being cached. This feature is applicable only to Windows. 5. Under Connections, click '+' to define a new connection. 6. Enter a name and, optionally, a description for this connection. 7. Select a type for the connection and then specify the connection. Type can be any of the following: - **Policy Secure (802.1X)**: Select this type if the connection establishes connectivity to an 802.1X wired or wireless device. - **Connect Secure or Policy Secure (L3)**: Select this type to define a connection for Ivanti Connect Secure or Ivanti Policy Secure. 8. The connection configuration options that appear depend on the connection type you select. After you have created the client connection set: - create a client component set and select this connection set. - open this saved connection set and create sub connection set for it. ### Configuring Client Certificate Selection Option While Configuring Ivanti Connect Secure settings, the following are the new checkboxes added under Client Certificate Selection Option. - Accept certificates with smartcard logon EKU - Accept certificate with Custom EKU text - Accept certificate with Custom EKU OID The valid certificates get filtered based on the specifications provided by administrator in the above fields. Only the filtered certificates get displayed in certificate selection prompt. To configure Certificate Matching and Certificate Ranking under Client Certificate Selection Option, the administrator needs to follow the below steps. 1. Go to **Users > Ivanti Secure Access Client > Connections**. 2. Select the connection from the Connections or click "+" to display the New Connection set configuration page. 3. Complete the configuration as required. 4. Save the configuration. If the **Prefer smart card certificate** option is selected, then certificates with client auth EKU set get displayed on the top of the list of certificates and preferred over other certificates. The **Accept certificates with smartcard logon Enhanced key Usage** option is enabled by default. This enables you to use Yubikey as PIV smart card for VPN authentication. Based on the EKU configuration settings, Ivanti Secure Access Client will pick-up the available certificate and make successful connection. If end-user has more than one certificates, then Ivanti Secure Access Client will prompt the end-user to select the certificates to make successful connection. ### Ivanti Secure Access Client Connection is Established Options For all connection types, specify how the connection is established. The options vary according to the type of connection. Automatic connections include machine authentication and credential provider connections. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/LSsHsMKgTBw2CoAP_WYCt_cliconnectionestablished584x256.png" position="flex-start" size="58" width="584" height="256" initialPath="img/cli_connection_established_584x256.png" githubPath="img/cli_connection_established_584x256.png" darkWidth="584" darkHeight="256" showCaption="false"} Connections can be established using the following options. :::hint{type="info"} All connections that are configured to start automatically attempt to connect to their target networks at startup time. To avoid multiple connection attempts, be sure that only one connection is configured to start automatically, or configure location awareness rules. ::: - Modes: - **User**: Enables user authentication. - **Machine**: Enables machine authentication, which requires that Active Directory is used as the authentication server and that machine credentials are configured in Active Directory. A machine connection is, by default, an automatic connection. - **Machine or user:** Enables machine authentication for the initial connection. After user authentication, the machine authentication is dropped. When the user logs out, the machine authentication connection is restored. - Options: - **Connect automatically:** Connections are attempted when the conditions specified in the location awareness rules are true, and disconnected when the conditions are no longer true. - **Reconnect at Session Timeout or Deletion:** If this option is enabled, user initiated sessions automatically attempt to reconnect upon a session timeout or deletion. If this option is disabled, then user initiated sessions remain disconnected upon a session timeout or deletion. - **Enable pre-desktop login (Credential provider):** Enables Ivanti Secure Access Client interaction with the credential provider software on the endpoint. The user credentials are used to establish the authenticated Ivanti Secure Access Client connection to the network, login to the endpoint, and login to the domain server. - **Disconnect tunnel on smart card removal:** Disconnects the tunnel when the smart card used for client certificate authentication is removed. This is not enabled by default. :::Paragraph{indent="2"} This feature works only when the primary authentication server is configured for certificate authentication, and the client certificate authentication is performed using a smart card certificate or when the realm is configured with certificate restriction and fulfilled with a smart card certificate. ::: :::hint{type="info"} The Disconnect tunnel on smart card removal configuration is applicable only when performing client certificate authentication with a smart card certificate in the ISAC client, even if it is enabled on the ICS. ::: :::hint{type="info"} The smart card's user certificate must include the smart-card-logon OID for this feature to function. ::: ### Creating a Client Component Set for Ivanti Connect Secure To create a Ivanti Secure Access Secure Client component set: 1. Select **Users > Ivanti Secure Access Client > Components**. 2. Click '+' to create a new component set. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/WYebXZQ38m2WcPH1sLgAz_clicomponentset571x276.png" alt="img/cli_component_set.png" position="flex-start" size="57" width="571" height="276" initialPath="img/cli_component_set_571x276.png" githubPath="img/cli_component_set_571x276.png" darkWidth="571" darkHeight="276" showCaption="false"} 3. If you have not yet created a client connection set, select **Users > Ivanti Secure Access Client > Connections** and create a new connection set. Or you can use the default client configuration, which permits dynamic connections, and allows Ivanti Secure Access Client to automatically connect to Ivanti Policy Secure or Ivanti Connect Secure. 4. Specify a name for the client component set. 5. (Optional) Enter a description for this client component set. 6. Select a connection set that you have created, or use the default connection set. 7. For Ivanti Secure Access Client components, select one of the following options: - All components: Supports all Ivanti Secure Access Client connection types. - No components: Updates existing Ivanti Secure Access Client configurations, for example, to add a new connection. Do not use this setting for a new installation. 8. Click **Save Changes**. 9. After you create a component set, distribute Ivanti Secure Access Client to users through a role. When users access the role, the installer automatically downloads to the endpoint. The installer components and connections are applied to the endpoint client. - If client connections associated with the component set for a role are changed even though the list of components has not, the existing configuration on the endpoint is replaced immediately if the endpoint is currently connected, or the next time the endpoint connects. - If a user is assigned to multiple roles and the roles include different component sets, the first role in an endpoint’s list of roles is the one that determines which client (component set) is deployed. ### Manage Ivanti Secure Access Client Versions This feature is supported for Ivanti Secure Access Client on macOS and Windows, and supported for iOS Mobile Client and Android Mobile Client also. This feature allows admin to configure a minimum client version. If the client has version lower than the configured minimum version, then the ICS server will reject the client connection. User can upgrade it later through browser or SCCM server. To enable this feature on Ivanti Connect Secure: 1. From the admin console, select **Users > Ivanti > Components**. 2. Select the **Enable minimum client version enforcement** check box. The following options appear: - Desktop Clients (Windows) - Desktop Clients (MacOS) - Android Mobile Clients - iOS Mobile Clients ![](https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/qqDxRl0jxhHE56La2GNsH_image.png) 3. By default, Cross-Platform package is activated for Windows, MacOS and Linux platforms. To activate a different package version for all the Desktop clients: 1. From the **Cross-Platform** Version list, select the appropriate version. 2. Click **Activate **and then click **Save Changes**. To activate a different version for Windows/MacOS platform: 1. Select the **Windows **tab / **MacOS** tab. 2. From the **Version **list, select the appropriate version. 3. Click **Activate **and then click **Save Changes**. ![](https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/S_6Y8U4hEKoldA7H-HLqV_image.png) 4. To force the Ivanti Secure Access Desktop Clients to upgrade with the newly activated version, click the **Force upgrade Ivanti Secure Access Desktop Clients** check box. 5. Click **Save Changes.** 6. Verify the Admin Logs for the activation and package download related logs. :::hint{type="info"} ICS Gateway imports only active ISAC package versions and deletes all existing ISAC packages except the Default package. This behavior also applies to platform-specific packages. Therefore, when an ICS Gateway administrator imports a user.cfg file from version 25.1.3.x or earlier, the existing platform-specific packages are deleted because none are active for those platforms. From 25.1.4.0 version to a new version, ICS Gateway will import all active packages for cross-platform, Windows, MacOS, and Linux platforms. ::: ## Enterprise Onboarding :::hint{type="info"} For ICS 25.x Gateways, this feature is deprecated and will be removed in the near future. ::: Enterprise onboarding allows users to securely access enterprise network resources with almost any device. WiFi, VPN and certificate profiles can be defined for enterprise resources and downloaded to a device during onboarding, depending on the device type. The profiles can be defined on a single Ivanti Connect Secure server dedicated to onboarding or they can be defined on each server. Alternatively, the profiles can be defined on a third-party MDM server, in which case users will see a link and instructions on the onboarding page to continue onboarding using the external MDM server. Onboarding is initiated from the browser. The supported profiles depend on the device type and whether the Ivanti Secure Access Client is installed. Device Onboarding Profile supports: - Android 4.0 or later: Supports all profiles, but the Ivanti Secure Access Client must be installed during onboarding. - iOS 6.0 or later: Supports all profiles (Safari browser). - Windows 7.0, 8.0, and 8.1: Supports WiFi and certificate profiles (IE, Firefox, or Chrome browser). The Ivanti Secure Access Client onboarding application must be installed during onboarding. Windows 8 RT and Windows 8 Phone are not supported. - MAC OS X: Supports WiFi and certificate profiles (Safari browser). Enterprise onboarding is enabled in the user role, and each profile can be applied to all user roles or specific roles. The SCEP server and CSR templates allow certificates to be generated dynamically for device and server authentication. ### Defining the SCEP Server The Simple Certificate Enrollment Protocol (SCEP) server configuration and CSR templates allows each client device to dynamically obtain certificates for authentication. To define the SCEP server: 1. Log into the NSA as a Tenant Admin. 2. From the Ivanti Connect Secure menu, click the **Gateway > Gateway List** and then select any standalone ICS Gateway. 3. Navigate to **Users > Enterprise Onboarding**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/6w0n_MkpK7HbLSXkyCdyv_onboardscep568x407.png" alt="img/onboard_scep.png" position="flex-start" size="57" width="568" height="407" initialPath="img/onboard_scep_568x407.png" githubPath="img/onboard_scep_568x407.png" darkWidth="568" darkHeight="407" showCaption="false"} 4. Enter the URL for the SCEP server. 5. Specify the password required by the SCEP server. 6. Specify the number of attempts to access the server when the first attempt fails. 7. Specify the number of seconds between retry attempts. 8. Click Browse to upload the certificate used to encrypt SCEP requests. To upload the certificate automatically, select the Test Enrollment check box, select a CSR template, and click **Test Configuration**. 9. Click **Save Changes**. ### Defining CSR Templates If the SCEP server is configured, the Certificate Signing Request (CSR) templates can be used in the VPN, WiFi, and certificate profiles to allow each onboarded device to dynamically obtain certificates for authentication on all mobile devices. Up to 10 templates can be defined. To define CSR templates: 1. Navigate to **Users > Enterprise Onboarding** and select **CSR Templates**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/KLe7XprpgX5xu-maSC5hW_onboardcsr568x230.png" alt="img/onboard_csr.png" position="flex-start" size="57" width="568" height="230" initialPath="img/onboard_csr_568x230.png" githubPath="img/onboard_csr_568x230.png" darkWidth="568" darkHeight="230" showCaption="false"} 2. Click '+' to add a new template. 3. Enter a unique template name. 4. Specify the subject distinguished name. For example: CN=\,OU=Engineering=Ivanti 5. (Optional) Specify an email address with the \ variable, such as \@ivanti.com. 6. Select an alternative name type if the CA requires an alternative subject name. 7. Specify one or more values for the selected alternative name type. Multiple values must be separated by a comma or space. 8. Select the key size used by the SCEP server. 9. Click **Save Changes**. ### Defining VPN Profiles VPN profiles provide Android and iOS devices with secure access to enterprise networks. One or more VPN profiles can be assigned to specific user roles or to all roles. Up to 10 profiles can be defined. To define VPN profiles: 1. Navigate to **Users > Enterprise Onboarding** and select **VPN Profiles**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/2cRv6fGyCSs1945NUs_d9_onboardvpn565x576.png" alt="img/onboard_vpn.png" position="flex-start" size="56" width="565" height="576" initialPath="img/onboard_vpn_565x576.png" githubPath="img/onboard_vpn_565x576.png" darkWidth="565" darkHeight="576" showCaption="false"} 2. Click '+' to add a new VPN profile. 3. Enter a unique name for the VPN profile. 4. (Optional) Enter a description of the VPN profile. 5. Select the device types the profile applies to (Android and iOS only). 6. Specify the URL of the VPN server. 7. Specify the realm name. The realm is required only if the sign-in URL has the User picks from a list of authentication realms option enabled. 8. Specify the user role. The user role is required if the role mapping rules for the user realm specify multiple roles and the User must select from among assigned roles option is enabled. 9. Specify the \ variable for the user name. 10. Select Password or Certificate for the user authentication method. 11. Select one of the following options: - Policy applies to ALL roles - To apply this profile to all users. - Policy applies to SELECTED roles - To apply this profile only to users who are mapped to roles in the Selected roles list. Make sure to add roles to this list from the Available roles list. - Policy applies to all roles OTHER THAN those selected below - To apply this profile to all users except for those who map to the roles in the Selected roles list. Make sure to add roles to this list from the Available roles list. 12. Click **Save Changes**. ### Defining WiFi Profiles WiFi profiles provide Android, iOS, MAC OS X, and Windows devices with secure access to wireless networks. One or more WiFi profiles can be assigned to specific user roles or to all roles. Up to 10 profiles can be defined. To define WiFi profiles: 1. Navigate to **Users > Enterprise Onboarding** and select **WiFi Profiles**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/T_LB7A1w1-YhhiHVjZXNO_onboardwifi571x649.png" alt="img/onboard_wifi.png" position="flex-start" size="57" width="571" height="649" initialPath="img/onboard_wifi_571x649.png" githubPath="img/onboard_wifi_571x649.png" darkWidth="571" darkHeight="649" showCaption="false"} 2. Click '+' to add a new WiFi profile. 3. Enter a unique name for the WiFi profile. 4. (Optional) Enter a description of the profile. 5. Select the device types the profile applies to (Android, iOS, MAC OS X, and Windows). 6. Specify the server set ID of the wireless network. 7. Select the **Non-Broadcast SSID** check box if the wireless network does not broadcast its identity. 8. Select the **Auto Connect** check box to connect the client automatically when the network is detected (not supported by Android clients). 9. Select the type of authentication used by the network, and specify the password or enterprise settings, as required. 10. For the WPA Enterprise and WPA2 Enterprise security types, select the supported EAP protocols and specify the associated authentication settings. 11. The PEAP protocol is supported by all clients. Specify inner authentication method, username and password, outer identity, Trusted Server name, Trusted CA certificate. 12. The EAP-TLS protocol is supported by all clients. Specify User name, CSR template, IP address or FQDN name, Trusted CA certificate. 13. The TTLS protocol is supported by all clients. Specify inner authentication method, username and password, Trusted Server name, Trusted CA certificate. 14. Select a role from Policy applies to ALL roles, Policy applies to SELECTED roles, Policy applies to all roles OTHER THAN those selected below. 15. Click **Save Changes**. ### Defining Certificate Profiles Certificate profiles specify the device certificates sent to each client device during onboarding. Up to 10 profiles can be defined. To define certificate profiles: 1. Navigate to **Users > Enterprise Onboarding** and select **Certificate Profiles**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/lZncJEwoMY84dmGorngeK_onboardcert577x606.png" alt="img/onboard_cert.png" position="flex-start" size="58" width="577" height="606" initialPath="img/onboard_cert_577x606.png" githubPath="img/onboard_cert_577x606.png" darkWidth="577" darkHeight="606" showCaption="false"} 2. Click '+' to add a new certificate profile. 3. Select the device types the profile applies to (Android, iOS, MAC OS X, and Windows). 4. Select the **Import and Use Global Certificate** option to use the Ivanti Connect Secure global certificate to authenticate the client device. Click **Import Certificate & Key**, click **Browse** to locate the certificate file, and then click **Import**. 5. Select the **Import and Use CA Certificate** option to import any CA certificate (public Root CA, private Root CA, public intermediate CA, or private intermediate CA). These CA's can be used in WiFi profiles and must be downloaded to the client devices. Click Import and Use CA Certificate, click **Browse** to locate the certificate, and then click **Import CA Certificate**. 6. Select the **Generate per User Certificate** option to use the SCEP server and a CSR template to generate a certificate for each client. Select a CSR template from the Use Certificate Template list. 7. Select a role from Policy applies to ALL roles, Policy applies to SELECTED roles, Policy applies to all roles OTHER THAN those selected below. 8. Click **Save Changes**. ### Defining Secure Mail To define secure mail: 1. Navigate to **Users > Enterprise Onboarding** and select **Secure Mail**. ::Image[]{src="https://api.archbee.com/api/optimize/wxZG1KsS4xNkVZYoiu_o9/V85GZcUlBKvA-iVyC2Yl3_onboardmail570x595.png" alt="img/onboard_mail.png" position="flex-start" size="57" width="570" height="595" initialPath="img/onboard_mail_570x595.png" githubPath="img/onboard_mail_570x595.png" showCaption="false"} For the configuration details, see [Secure Mail](docId\:q2SWzExiSq6OxuG47Wuyb).