Create a Connector

To create a new connector:

1. On the Connectors page, click the Create button.

NOTE: To edit a connector, double-click its entry or select the connector and click the Edit button.

2. Select a Connector Type.

3. Accept the Terms and conditions.

4. Configure settings on the Overview, On-demand, Settings, Releases tabs (settings described below).

Global Settings on the Overview tab

On the Overview tab, give the new connector a name, choose whether it is Enabled, and configure its global settings:

• Direction -  Determines in which direction the connector sends information:
  • Push - The connector will create packages in the remote system.
  • Pull - Packages can be created from resources or imported from the remote system
• Synchronization Method - Determines how the connector should be synchronized.
  • On-demand - Synchronizes only the packages you created based on the connector resources.
  • Synchronize - This option will automatically synchronize all packages with new available information.
• Stage
  • Development
  • Test
  • Acceptance
  • Production
• Package name prefix - The default prefix used for the names of the new packages from the connector, which will help you to easily identify all packages originating from a certain connector.

On-demand settings

On the On-demand tab, set the package type.

• Default package type - This option determines the way a package will be handled after creation:
  • Managed - the package is eligible for automatic updates and it has an action set that is locked for editing. You are still able to add new action sets to this package.
  • Unmanaged - the package is not eligible for automatic updates and no locked action sets are added.

Connector-specific settings

For options you'll need to configure on the Settings tab, see the articles for each connector type.

• Citrix StoreFront
• Application Workspace Setup Store
• Application Workspace
• Microsoft Azure Virtual Desktop
• Microsoft Print Server
• Microsoft RDS
• Microsoft Store
• Microsoft System Center Configuration Manager
• Nutanix Frame
• Okta
• Omnissa Horizon

Entitlement settings

On the Entitlements tab, manage entitlements on packages created via the connector. This allows you to assign a default set of entitlements for all connectors. Some connectors support importing entitlements from the remote system.

NOTE: This tab is available only when the connector is set to use the synchronized method.

Import entitlements

With the import entitlements functionality enabled, you can add policies to match an identity (user, group, device or device collection) configured in the remote system with an identity known within Liquit.

Overview tab

• Identity Source - The Application Workspace identity source to match users and groups from the remote system.
• Applies To - Which Application Workspace identity types (user, group, context, device, device collection) inside the selected identity source should be matched.
• Property - The property of the Application Workspace identity to use when matching with the remote system.

Value transformation tab

• Compare - What operator needs to be used on the property selected in the Overview tab.
• Match - The regex used to match part or all of the properties from the remote system; use .\* to match all of the properties.
• Result - The value to compare against the regular expression's result. To match against the exact same property, use ${0}. To match against a different property from a Liquit Identity, use one of the predefined identity variables that appear in the drop-down list of the field when you try to edit it. See Variables for a complete list of all predefined variables within Application Workspace.

Settings tab 

Keep the default settings for publishing packages on the user's devices or override them. See Packages for more information.

Manual entitlements

With the manual entitlements functionality enabled, you can add entitlements manually by selecting the Add static button in the table toolbar.

In the Overview tab select the Application Workspace identity (user, group, context, device or device collection) you want to entitle.
In the Settings tab keep the default settings for publishing packages on the user's devices or override them. See Packages for more information.

8. On the Synchronization profiles tab, specify whether the Application Workspace System or the remote system is controlling some of the packages' information.

Available Options:

• Synchronize from connector - If the entity exists in Application Workspace, it is updated with the value provided by the remote system. Application Workspace will not attempt to create entities if they don't exist.
• Synchronize from connector, create entity if not exist - Updates the existing entities and creates new entities if they don't exist in Application Workspace yet.
• Set from connector during creation - Updates the existing entities and creates new entities if they don't exist in Application Workspace yet. Uses the value provided by the remote system only initially and it can be modified without it getting changed by the connector afterwards.
• Create entity from connector during creation - Associates entities and creates new ones if they don't exist in Application Workspace yet. The entities can be modified after creation without them getting changed by the connector afterwards.
• Static - If you select this option, an adjacent empty field or check box appears, that lets you configure a permanent value for this package option.
• Ignore - Never retrieve the value/entity from a remote system.

Release settings

This page allows you to define the way releases should be created on packages. For more information about each type of publishing stage see Packages.

NOTE: The Test and Acceptance stages are available only when you have a Release and Patch Management license.

Available Options:

• Publish - Choose the stage to which the packages are published by default.
• Enable release retention - Enables the Remove releases older than and Keep number of releases sections on this screen.
• Remove releases older than section - Set the number of days after which the releases are automatically removed.
• Keep number of releases section- Set the number of releases that should be preserved.