Enhancements in Accops Workspace Linux Client version 7.2.1.1008

UK Character Support for Workspace Client Login

Workspace Client authentication has been enhanced to fully support UK-specific and extended character sets.

Previously, certain UK special characters were not processed correctly during authentication and password management operations. This release resolves those limitations.

Supported fields include:

• Username

• Password

Users can now successfully authenticate with credentials that contain supported UK-specific characters.

Password Change Support

Password change operations have also been enhanced to support UK special characters.

Key Benefits

• Improved compatibility with regional and organizational password policies.

• Successful authentication using credentials containing UK-specific characters.

• Reliable password change and reset operations.

• Improved user experience for UK-based and multilingual deployment environments.

Desktop Folder Grouping for VDI Pools

Desktop Pool configuration now supports folder grouping, allowing administrators to organize published desktops into folders for improved workspace management.

This functionality is similar to application folder grouping and provides better organization of Shared Hosted Desktop (SHD) and Virtual Desktop Infrastructure (VDI) resources.

Configuration Location

HyWorks Controller

Location	Path
Management Console	HyWorks Controller Management Console > VDI > Pools > Add/Edit Desktop Pool wizard > Client Settings tab > Folder Creation

Folder Creation Options

Option	Description
None	Desktops are published without folder association.
Create New	Create a new folder and associate desktops with it.
Use Existing	Associate desktops with an existing folder.

Key Benefits

• Improved desktop organization.

• Better separation of SHD and VDI resources.

• Cleaner workspace presentation for end-user.

• Consistent desktop grouping across environments.

Important Limitations

Constraint	Details
No explicit folder management	Folder association can ONLY be done through the Add/Edit Desktop Pool wizard.
Folder deletion is not supported	Folder deletion is not supported from the management console.
Application ≠ Desktop folders	Application folders and desktop folders are independent and cannot be shared.

Power Operation Control for Virtual Desktops

Power Operation Control enables administrators to control which desktop power operations are available to end users.

This feature provides centralized management of desktop lifecycle operations directly through HyWorks.

Configuration Location

HyWorks Controller

Location	Path
Management Console	HyWorks Controller Management Console > VDI > Pools > Add/Edit Desktop Pool wizard > Client Settings tab > Power Operation Control

Configuration Options

Option	Description
Allow All	All supported power operations are available to end users, subject to the VM's current power state.
Disable All	All power operations are hidden or disabled regardless of the VM's power state.
Allow Limited	Only administrator-selected power operations are available, based on the VM's current power state.

Important Restriction

This feature is supported only for single-session desktops.

Power Operation Control is not available for:

• Multi-session desktops

• Shared desktop environments

Key Benefits

• Centralized administrative control.

• Reduced risk of accidental user-initiated power operations.

• Improved compliance with operational policies.

Greater flexibility in managing desktop lifecycle actions.

SAML WebView Cache Cleanup After Login Completion

The SAML WebView Cache Cleanup feature allows administrators to control whether the client clears the SAML WebView cache after successful SAML authentication.

This behavior is managed through the Gateway Configuration Service using the globalclientsetting.js configuration file.

The feature provides greater control over SAML session management and helps prevent issues caused by stale authentication data.

Key Benefits

When enabled:

• The client automatically clears the SAML WebView cache after a successful login.
• Stale or cached SAML sessions are removed.
• Authentication failures caused by outdated session data are reduced.
• Session conflicts between consecutive logins are minimized.
• Security is improved by preventing retention of SAML session information.

Default Behavior

• The feature is disabled by default (flag = false).
• Cache cleanup occurs only when explicitly enabled in globalclientsetting.js.
• The setting is applied immediately after the client retrieves the realm configuration details from the Gateway.

Configuration

Configuration Tag in globalclientsetting.js:

Tag	Description
CLEAR_WEBVIEW_SAML_CACHE_ON_COMPLETE = true	- Clears the SAML WebView cache after successful authentication. - Prevents issues caused by stale or cached SAML sessions. - Users must re-authenticate during subsequent SAML sessions. - Improves security by removing retained session data.
CLEAR_WEBVIEW_SAML_CACHE_ON_COMPLETE = false	- Retains the SAML WebView cache. - Existing session and credential information may be reused. - Provides faster authentication for repeat logins. - Maintains existing behavior (default setting).

SAML Login Workflow

• The user initiates SAML authentication.

• The SAML WebView dialog is launched.

• The user completes authentication.

• Login processing completes successfully.

Cache Cleanup (when enabled)

After successful authentication:

• The client evaluates the SAML_CACHE_CLEAR setting.

• If enabled (true), the client invokes: webProfile.clearHttpCache().

• The WebView cache is cleared before the WebView is closed.

Default WebView Profile Fallback

A fallback mechanism has been added for environments where SAML WebView cache cleanup is disabled.

When cache cleanup is not enabled, the client will use the Default WebView profile instead of a specialized SAML WebView profile that relies on cache-clearing behavior.

Behavior When Cache Cleanup Is Disabled

Configuration

CLEAR_WEBVIEW_SAML_CACHE_ON_COMPLETE = false, or when the setting is not configured.

Result

• The client does not invoke webProfile.clearHttpCache().
• Cached HTTP content and session data remain available.
• Existing SAML session information can be reused during future authentication attempts.

Fallback Logic

When CLEAR_WEBVIEW_SAML_CACHE_ON_COMPLETE is set to false:

1. The client detects that SAML cache cleanup is disabled.
2. The specialized SAML WebView profile is not used.
3. The client automatically falls back to the Default WebView profile.
4. Authentication continues using the standard WebView configuration.

Benefits of the Fallback

• Provides consistent behavior when cache retention is required.
• Eliminates dependencies on SAML-specific WebView profiles designed for cache-clearing workflows.
• Improves compatibility across different authentication environments.
• Simplifies WebView profile management and reduces configuration complexity.