Omnissa Unified Access Gateway Release Notes

Unified Access Gateway 2406 | 24 JUL 2024
Check for additions and updates to these release notes.

Unified Access Gateway appliance helps enable secure remote access for virtual desktops, internal sites, applications, and file repositories users. To learn more, see the Unified Access Gateway Documentation at Omnissa Product Documentation.

Omnissa Unified Access Gateway Release Notes provides information about the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues that are reported in each version.

What's New

Unified Access Gateway 2406 provides the following new features and enhancements:

Added support for Horizon Connection Server’s Home Site Redirection feature (associated with Cloud Pod Architecture), which helps to reduce backhaul traffic by redirecting users from a connected site to their designated home site. This traffic to home site is validated by Unified Access Gateway before entering the corporate network. For more information, see Enable Re-authentication in Home Site in the Configure Horizon Settings.

Added support for Basic and NTLM authentications in outbound proxy configuration.

When deploying on Azure, Unified Access Gateway VM, Virtual Network, Network Security Group (NSG) and public IP address can now be deployed in different Azure resource groups.

Improvements to SNMP configuration functionality - allows the retention of SNMP configuration settings for Tunnel even when SNMP is reconfigured with different parameters.

HTTP cookies set by Unified Access Gateway will now have SameSite attribute set to Lax.

Added support in PowerShell script to enable/disable monitoring of unrecognized sessions using the new field unrecognizedSessionsMonitoringEnabled. See PowerShell deployment parameters.

Enhancements to adminreset command line utility. See Recover the Admin using the adminreset Command.

Workspace ONE Tunnel

The Workspace ONE Tunnel gateway can now be deployed as a Container outside of Unified Access Gateway. See Workspace ONE Tunnel Container Release Notes and Deploying with Tunnel Container.

Update log format from plaintext to JSON, which enables simplified integration with log filtering solutions like Splunk, Elasticsearch, and so on.

Improvements to bulk sync retry logic to account for intermittent policy sync failures.

Ability to control the OpenSSL signature algorithm for Workspace ONE Tunnel via KVP openssl_signature_algorithms specifies the signature algorithms allowed in handshake between devices and the gateway.
- Default Value:auto
- Accepted Values: RSA+SHA256:RSA+SHA384. You may use a colon (:) to separate accepted values.

Logging improvements and troubleshooting enhancements.

Updates to OS package versions and Java component versions. These updates include OpenSSH version update to remediate a vulnerability CVE-2024-6387.

Before You Begin

Compatibility Notes
For more information about the compatibility of Unified Access Gateway with other products, see Product Interoperability Matrix.
Install and Upgrade
To download the Unified Access Gateway, see the Product Download page.

Resolved Issues

Note: The numbers included before the resolved issues are used for internal issue tracking.

UAG-9094: If an IP address does not get assigned to a network interface during deployment, network settings for that interface cannot be changed from the Admin UI.
UAG-10389: If session timeout is set to 0, users cannot connect to Horizon entitlements.

UAG-10820: Intermittent CPU spikes when authentication method is set to X.509 Certificate or RADIUS.

UAG-10388: After deployment on Hyper-V, IP address does not get assigned to the network interface.

UAG-10607: Deploying Unified Access Gateway using PowerShell reports error when the secureRandomSource field is set to “Default” in the .ini file.

UAG-10499: The tunnel service is not coming up if outbound proxy is configured on Tunnel edge settings.

UAG-10369: When configuration is imported using .json file, monitoring of unrecognized requests feature is not disabled though this condition is specified in the .json file.

UAG-10363: Configuration changes made on the Network Settings window on the Admin UI take effect but does not reflect on the UI and in the exported .json and .ini files.

UAG-10386: Non-standard TLDs (like .itm) cannot be specified in Horizon Settings > Host Port Redirect Mappings.

PPAT-16108: Tunnel service restart due to incorrect parsing of server KVP.

PPAT-16421: Auto-restart Tunnel service on keepalive_timeout KVP update.

Known Issues

Note: The number(s) included before the known issues are used for internal issue tracking.

UAG-10906: Logs in syslog server (if configured) will show hostname as ipv6-localhost.

To work around the issue:

Option 1:

Login to console as root user.
Remove the following lines from the /etc/hosts file:

::1 ipv6-localhost ipv6-loopback 127.0.0.1 localhost.localdomain 127.0.0.1 localhost

Restart the syslog-ng service.
systemctl restart syslog-ng

Option 2:
i) When deploying using PowerShell script:

Add the following entry in the [General] section of .ini file. This option is useful during automated deployments, with the workaround integrated into the deployed appliance.
[General] commandsFirstBoot=sed -i -e '/::1[[:space:]]*ipv6-localhost[[:space:]]*ipv6-loopback$/d' -e '/127.0.0.1[[:space:]]*localhost.localdomain$/d' -e '/127.0.0.1[[:space:]]*localhost$/d' -e '/127.0.0.1[[:space:]]*photon$/d' -e '/127.0.0.1[[:space:]]*photon-machine$/d' /etc/hosts

ii) When deploying using vSphere Client or vSphere Web Client:

Add the same entry in the Commands to Run During First Boot field of the OVF template wizard.

Documentation

Documentation for Unified Access Gateway is located at Omnissa Product Documentation.

Support Contact Information

To receive support, access Customer Connect.

For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the Knowledge Base (KB) article 6000005.

Localized Content for Omnissa Docs

The transition from Broadcom to Omnissa is in progress. As part of that transition, we are reviewing our localization strategy for how best to serve the needs of our customers and partners. We will be providing localized version of Omnissa Docs content again soon. Thank you for your patience.

Transition Update

The transition from Broadcom to Omnissa is currently in progress (see announcement), and the migration to new resource portals and localization is underway. We are making significant efforts to ensure that the URLs and resources remain up to date.

Was this page helpful?