3.0

3.0.1607

Changes

• Add Created at / Modified at values to snapshot details
• Performance enhancement
• Show which permissions are given for each privilege when assigning a team privilege

Bugfixes

• Missing icon in side menu when creating a new team
• Adding an duplicate identity in teams doesn't update the existing row
• Remote Control option is not available within contacts screen when no agent is installed
• Unable to configure "Sequential, ignore errors" within Action Sets
• Mark client secret as not required for AD FS
• Remote control produces a javascript error
• Initiating a remote control session showed all hidden packages
• Can't search through devices and servers
• Can't create a new zone without "modify zone" privileges

3.0.1600

Bugfixes

• Search bar could overlap with detail view in contacts
• Unable to create a new user when no privileges were set on Identity Sources
• High CPU usage when multiple agents are refreshing
• Team icons were missing when using the agent
• Fix error message if no upload privileges are set
• Download button on uploaded registry file
• Credentials were unavailable during deployments

3.0.1596

Changes

• Added support for the french language in the setup store.
• Changed "No agent required" option on packages to "Agent required"
• Added support for caching small content files in memory.

Bugfixes

• Some disabled elements have a different styling.
• Search icon issues on iOS devices.
• Switching between type of task schedule will reset the time to 8:00.
• Missing icons on introduction screen.
• Missing combobox options in the setup store configuration wizards.
• Device keeps reporting distribute and install events even when they are already installed.
• "Service Exists" and "Service State" filters doesn't work on service display name.
• Unable to save context with a subnet filter with the "Agent" option enabled.

3.0.1590

Bugfixes

• Server content path setting isn't migrated when upgrading from 2.6 to 3.0.
• Removing the last approver causes all pending approvals to get stuck in pending state.
• When an approval gets rejected, the rejection message won't be mailed to the end user.
• Identity Source modification privileges are needed to add, remove or modify local users.
• ShellAPI doesn't display error during launch when the progress bar is hidden.
• Unable to monitor task in a different zone (Install License/Refresh license).
• SSO configured in the URL returns "An untrusted source attempted to request access".
• ShellAPI could cause excessive CPU load when waiting for a task to complete.
• Missing "country" field within contacts.
• Hide "Display Name" and "Name" fields from Identity Source filters.

3.0.1585

Bugfixes

• Agent tasks under diagnostics isn't working.
• Default agent download setting has been changed to MSI.
• User cannot be opened immediatly after adding a LOCAL user.
• Default agent.xml contains device registration configuration.
• Prevent overflowing text from disforming the snapshot boxes.
• Connector synchronizer task not properly breaking lines in details for mails.
• Upgrade to 3.0 fails during attribute migration.
• Unable to view action set details if it can't be edited.

3.0.1582

Bugfixes

• Added support for user settings within the Workspace Integration API.
• Connector updates doesn't include package icons.
• Unknown error is displayed when unable to read resources, without details.
• Content cleanup task can timeout when the database is too large.
• Show active apps setting for catalog has no effect.
• Workspace Integration API doesn't support non-primary zones.
• Login only (launcher disabled) doesn't properly handle offline mode.
• Tags not visible on workspace with user privileges.
• DNS resolve messages are shown in log even when Agent Load Balancing mode is disabled.
• Workspace package launch error messages aren't user friendly.
• Error details isn't visible within the events view.
• Native icons aren't working properly with the 3.0 agent.
• Agent won't try to redownload content if the initial request fails.
• Actions with content fail to import from a Liquit Workspace 3 connector.

3.0.1577

Bugfixes

• Teams without an uploaded icon has the default team icon shown at the end instead of the front.
• Selecting the same access policy again on a user, group or context and saving the (change) results in access policy being removed.
• Missing deployment icons in context, collection and device views.
• Missing default package icons in license, tag and deployment views.
• Missing icons in the user portal teams and credentials lists.
• Its possible to assign an authenticator to the LOCAL identity source.
• Unable to delete zone when an custom context is created within the zone.
• Unable to delete server because of a database error.
• Its possible to select two side menu items within the workspace.
• Autocomplete is enabled for configuration password fields.
• PowerShell: When unable to connect to a second default workspace, results in previous session remaining active.
• PowerShell: Null exception is thrown when executing a cmdlet without a valid connection.
• When triggering a identity source refresh could enable the identity source if its disabled.
• Agent log level is forced to debug logging.
• When a corrupt agent.db is found, agent will not attempt to recover it.
• Inconsistent manufacturer names in MSI properties.

3.0.1572

General changes

• Liquit uses an all new REST based API for both management and workspace access.
• All name fields have been increased from a maximum length of 50 to 100 characters.
• Description fields have been added to all management objects.
• Liquit uses Access Tokens as a preferred method for authorization to replace session keys.

Agent

• Offline support
• Web links opened in the launcher now use the default browser instead of Internet Explorer

Workspace

• Sidemenu has been simplified, showing all available filters.
• Search has now been split up (Workspace, Catalog and Contacts) search requests to speed up results coming in as they are available.
• Default icons based on package types.
• Refresh button has been added
• Loader has been added to indicate a manual refresh is inprogress.
• Show progress when launching a package without agent.

Catalog

• Pending requests can be cancelled by the user.
• Approvals are now available in the catalog.
• Get/Request buttons have been added in the details view.
• Additional filters have been added.
• Refresh button has been added.

Login

• Login has been updated with a new UI.
• The identitySource URI parameter will now hide other identity sources.
• Support for Azure AD authentication based on login form or HTTP SSO.

Devices

• Additional columns have been added that can be selected in list view, including but not limited to: IP, Manufacturer, System Model.

Servers

• IP and listening ports can be modified using the new Server.json configuration file.

Mail Servers

• Multiple mail servers can now be configured.
• Servers can now be configured in Load Balancing groups.
  * Servers with the same priority are load balanced per request.
  * Server priority of 1 will be the preferred server that Liquit will use, unless a failure occurs.

Identity Sources

• Select which authentication methods are enabled. (Login, Federated, HTTP and NTLM)
• Move the order of preference of the authentication methods, to select which methods should be attempted first.
• OAuth2 configuration settings are now available under "Federated".
• Contact attributes can be hidden per identity source.

Identity Sources (LDAP)

• Active Directory and eDirectory have been merged into a single LDAP Identity Source
• Schema option has been added to the LDAP Identity Source to choice between AD or eDirectory schemas.
• Servers can now be configured in Load Balancing groups.
  • Servers with the same priority are load balanced per request.
  • Server priority of 1 will be the preferred server that Liquit will use, unless a failure occurs.
• Page size, Connection Time and Search Timeouts can be adjusted per server.
• Secure option has been moved from global to per server.

Identity Sources (Azure AD)

• Its now possible to use the Liquit UI as login option.
• Azure AD credentials can now be used to connect with the Liquit Workspace PowerShell module.

Authenticators

• Servers can now be configured in Load Balancing groups.
  * Servers with the same priority are load balanced per request.
  * Server priority of 1 will be the preferred server that Liquit will use, unless a failure occurs.

Contexts

Contexts replaces both the locations and dynamic device collection feature. These can be used to assign user permissions within Liquit and as a means to distribute deployments and packages. A user can belong to multiple contexts, context settings are applied in order.

• Filter based on user and/or device attributes.
• Override system wide variables.

Tags

Categories have been renamed to tags.

Deployments

• Packages can be assigned from device, collection or context objects.
• Package stage support has been added.

Remote Control

• Remote Control packages are now supported without an agent.
• Package filters are now being used to determine if package can be used.
• Packages need to be assigned as (Hidden) packages, remote control is not available on agents of version 2.6.4 or prior.

Scheduled Tasks

• Added the ability to add multiple schedules to a single task.
• Removed the option to add system level tasks.

Access Policies

Policies replaces roles feature, enabling per object permissions based on their attributes.

• There are two type of policies available:
  • Role - A traditional role based permissions system comparable to 2.x, that allows you to visually select what a person has permissions for.
  • Script - Create a custom script that allows you to control permissions based on attributes of a resource, to create per object permissions.
• New role privileges have been added for the workspaces, including privileges that can be controlled:
  • Upload content
  • View tags
  • View/post reviews
  • View/request catalog items
  • Reset workspace
  • Add/view/modify/remove teams
  • View/modify/remove credentials.
  • Accept/reject/view/remove approvals.
  • API access (PowerShell and Liquit Setup Commander)

Packages

• Package type field is now freely editable, no longer a fixed list of options.
• Added offline option to a package, to make the package available while the agent is disconnected from the Liquit Server, requires 3.0 agent.
• Added a "No agent required" option to enable this package for use without an agent running.
• Added release management functionality
• There are 4 stages available, namely;
  • Development - This a new version of the package can be created/modified.
  • Test - This is where a version is deployed to a select group of test users.
  • Acceptation - This is where a version is deployed to a select group of acceptation users.
  • Production - Deployed to all users within the organization.
• Stage in which a user or device belongs to can be configured within entitlements.
• Development stage (previously known as sandbox) can now be developed and deployed to select devices to test them before moving them to the next stage.
• Staging is only supported with the Liquit 3.0 agent or without an agent.
• Use Drag & Drop to move between stages.
• Select stages to see their current configuration.
• Distribute, Install, Launch and Uninstall action sets have now been moved into a single interface.
• Ability to add multiple action sets of a single type, to group actions.
• Disable entire action sets.
• Added additional event triggers under entitlements:
  • Agent startup
  • Device startup
  • On session connect
  • On session disconnect
  • On session lock
  • On session unlock
• Modify identity member is supported without agent.
• Packages can be assigned from user, group, device, collection or context objects.
• Browse for identity has been added to entitlements, allowing more sorting and filtering options.
• Package relationships can now be viewed at dependencies tab.

Connectors

• Managed packages
  • Can now be modified by adding new action sets while still retaining update functionality.
  • Action sets that are created by the connector cannot be modified.
• "Ignore missing dependencies" option has been added during the create and update package wizard.
• Connector can be configured to place updates in a specified stage.