Skip to main content

22 novembre 2026

Omnissa Unified Access Gateway Release Notes

Unified Access Gateway 2609 | 29 OCT 2026
Unified Access Gateway 2609.1 | 21 NOV 2026

Unified Access Gateway appliances provide users with secure remote access to virtual desktops, internal sites, applications, and file repositories. To learn more, see Unified Access Gateway Documentation.

Omnissa Unified Access Gateway Release Notes provide 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 - 2609.1

Security Updates

Updated security patch for OpenJDK package, which addresses CVE-2026-114938. For more information, see OMSA-2026-0003.

Bug Fixes

2609.1 includes fixes for several issues reported in version 2609. Ensure to review the Resolved Issues - 2609.1 section.

What's New - 2609

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

General

  • Redesigned Admin UI
    Unified Access Gateway 26.09 introduces a redesigned Admin UI that makes appliance administration faster and more intuitive. See Using the Admin UI Console.

    • Improved navigation and search: A new layout and cross-category search help administrators locate settings quickly.
    • Refreshed dashboard: The dashboard shows the health of edge services and appliance resource usage at a glance, with shortcuts to common administrative tasks.
    • Guided JSON configuration import with validation and preview, allowing administrators to review configurations before applying them and helping reduce configuration errors.
  • Strict client certificate validation
    The new Enable Strict Client Certificate Validation flag for X.509 certificate authentication applies additional checks to client certificates, including Extended Key Usage, Critical extensions, and stricter validity check during CRL/OCSP validation. See Configure certificate authentication > Enable Strict Client Certificate Validation.

  • Addressed the eMudhra key compromise issue and resolved the vulnerabilities tracked under CVE-2026-91403 and CVE-2026-114406 with the latest OS and Java security updates.

  • Logging and troubleshooting improvements

Horizon

  • Limited Availability (LA): Support for deploying Unified Access Gateway with Horizon 8 on Red Hat OpenShift
    As part of Horizon 8 support for OpenShift Limited Availability, administrators can deploy Unified Access Gateway on Red Hat OpenShift. For more information, see Omnissa Horizon 8 Release Notes and PowerShell deployment to Openshift.

  • Increased size limit for custom executables
    Unified Access Gateway increases the maximum supported size of custom executables from 200 MB to 500 MB. This helps administrators to install and upgrade packages that are bigger than the previous limit. See Client custom executables.

Behavior Changes

Before upgrading to 2609, ensure to review the following changes. Depending on your configuration, some changes might require updates to your environment. To prepare for the upgrade, use the pre-upgrade checklist in the Knowledge base article KB 6001863. Each item in the KB list states which configuration it affects.

  • Extended Server Certificate Validation: Enhancements for better RFC conformance in certificate validation flow. Applies only if this setting is enabled (default: disabled). See System configuration > Extended Server Certificate Validation.

  • CA thumbprint trust for outbound connections: Backend servers must present a complete certificate chain that ends at the configured CA.

  • Host header allow list: The Host header of each request must match the configured allow list. Requests that do not match are rejected with HTTP 400. See Host Header Validation on Unified Access Gateway.

  • SNMP: JSON import and PowerShell deployment prompt for the SNMP v1/v2c community name when SNMP v1/v2c is configured. This field is optional. If blank, the default (public) is used.

Before You Begin

Resolved Issues - 2609.1

  • UAG-14614: The Active Sessions count on the Admin UI dashboard remains 0 when Workspace ONE Tunnel sessions are active.

  • UAG-14612: File is not supported error in Identity Provider Metadata when reopening a saved Identity & Access configuration for editing, if the metadata was uploaded with the Entity ID field left blank.

  • UAG-14610: When configuration per network interface exceeds 10 static routes, it will not be applied.

  • UAG-14474: Deployment using an exported INI file might fail if there are additional quotation marks and escape characters in securityHeaders and other values containing a semicolon (;) or hash (#).

  • UAG-14578: Workspace ONE UEM Edge Services configuration fails when API server hostname is not resolvable.

  • UAG-14462: The Admin UI might display the error File type is not supported for a trusted certificate entry, even though the certificate is present and valid.

  • UAG-14622: Downloading SEG diagnostics from the Admin UI fails with 0 unknown error.

  • UAG-14651: Workspace ONE UEM Edge Services configuration fails due to mismatch in the allowed IP ranges for the API server.

  • UAG-14624: When deploying a FIPS-enabled UAG appliance with Enable DISA STIG compliance turned off, the login banner might briefly appear on the console during first boot.

  • UAG-14582: Admin UI SAML authentication fails when all signing certificates in the identity provider’s metadata have Basic Constraints set to CA:TRUE.

  • UAG-14510: Improve memory handling in the HTTPS request router to prevent memory leaks.

  • UAG-14626: Unable to configure Tunnel edge service if UAG DNS is unable to resolve the UEM API endpoint.

  • CMEM-187462: SEG may intermittently fail to configure due to an UEM API connection error.

  • PPAT-22942: Workspace ONE Tunnel service on UAG may become unresponsive due to a service deadlock.

Resolved Issues - 2609

  • UAG-13728: rootSessionIdleTimeoutSeconds does not extend Idle Shell Timeout.
  • PPAT-21429: Syslog over TCP fails when sent directly from Tunnel service.
  • PPAT-22611: Access logs using Syslog reported corrupted remote_host_ip and remote_host_port values for TCP tunnel flows (for example, "443]:443" instead of "443"). This is limited to logging, and traffic routing is not affected.
  • PPAT-22748: A deadlock condition on the Tunnel Server might cause a service disruption when a DTR policy refresh coincides with active session processing.

Known Issues - 2609

  • UAG-14474: Deployment using an exported INI file might fail if there are additional quotation marks and escape characters in securityHeaders and other values containing a semicolon (;) or hash (#).
    Workaround: See
    KB 6001890.

  • UAG-14462: The Admin UI might display the error File type is not supported for a trusted certificate entry, even though the certificate is present and valid.
    Workaround: This issue is limited to the UAG admin UI and has no functional impact. Currently, there is no workaround.

  • UAG-14622: Downloading SEG diagnostics from the Admin UI fails with 0 unknown error.
    Workaround: Currently, there is no workaround.

  • UAG-14651: Workspace ONE UEM Edge Services configuration fails due to mismatch in the allowed IP ranges for the API server.
    Workaround: Currently, there is no workaround.

  • UAG-14624: When deploying a FIPS-enabled UAG appliance with Enable DISA STIG compliance turned off, the login banner might briefly appear on the console during first boot.
    Workaround: This issue has no functional impact. Currently, there is no workaround.

  • UAG-14582: Admin UI SAML authentication fails when all signing certificates in the identity provider’s metadata have Basic Constraints set to CA:TRUE.
    Workaround: Use SAML Identity Provider signing certificate that have Basic Constraints set to CA:FALSE.
    Note: This change might impact other services if shared certificate is in use.

  • UAG-14578: Workspace ONE UEM Edge Services configuration fails when API server hostname is not resolvable.
    Workaround: See KB 6001863.

  • UAG-14510: Improve memory handling in the HTTPS request router to prevent memory leaks.
    Workaround: Currently, there is no workaround.

  • UAG-14659: Forwarding rule for TCP 443 added during deployment is not applied due to a conflicting nftables rule.
    Workaround: Currently, there is no workaround.

  • UAG-14626: Unable to configure Tunnel edge service if UAG DNS is unable to resolve the UEM API endpoint.
    Workaround: Currently, there is no workaround.

  • PPAT-22942: Workspace ONE Tunnel service on UAG may become unresponsive due to a service deadlock.
    Workaround: See KB 6001897.

  • CMEM-187462: SEG may intermittently fail to configure due to an UEM API connection error.
    Workaround: Retry the configuration. If the issue persists, contact Omnissa Support.

  • UAG-14614: The Active Sessions count on the Admin UI dashboard remains 0 when Workspace ONE Tunnel sessions are active.
    Workaround: This issue is limited to the dashboard display and has no functional impact. To view the actual session counts for UEM services, you can use Edge Service Session Statistics under Monitoring.

  • UAG-14612: File is not supported error in Identity Provider Metadata when reopening a saved Identity & Access configuration for editing, if the metadata was uploaded with the Entity ID field left blank.
    Workaround: This issue is limited to the UAG admin UI and has no functional impact. The saved configuration is not affected. Currently, there is no workaround.

  • UAG-14610: When configuration per network interface exceeds 10 static routes, it will not be applied.

    Workaround 1: Applicable when Admin SAML authentication is disabled
    Use the REST API to add the static routes for each network interface (eth0, eth1 or eth2). Replace <UAG Management IP or hostname> with the management address of the UAG appliance. curl will prompt for the admin password.
    1. Get the current settings of the network interface: curl -k -u admin -X GET 'https://<UAG Management IP or hostname>:9443/rest/v1/config/nic/<nic>' -H 'accept: */*'
    2. Update the network interface with the full list of static routes: curl -k -u admin -X PUT 'https://<UAG Management IP or hostname>:9443/rest/v1/config/nic' -H 'Accept: text/plain' -H 'Content-Type: application/json' --data-raw '{"nic": "<nic>","ipv4Address": "<ipv4Address>","ipv4Netmask": "<netmask>","allocationMode": "<allocationMode>","ipv4DefaultGateway": "<ipv4DefaultGateway>","ipv4StaticRoutes": "<route1>,<route2>,<route3>"}'
    3. Copy nic, ipv4Address, ipv4Netmask and allocationMode from the GET response.
    ipv4DefaultGateway applies to eth0 only. Include it only if it appears in the GET response.
    ipv4StaticRoutes is a comma-separated list. Each route has the form <network>/<prefix-length> <gateway> or <network>/<prefix-length>, for example 10.10.0.0/16 192.168.1.1. List all the routes you want, including the existing ones.
    Workaround 2: Pass static routes during deployment.

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.

Localization

For details on Omnissa’s localization strategy, see Announcing Omnissa Localization Support.

Was this page helpful?

Provide feedback for this topic

Was this topic helpful?

Please do not include any personal or confidential information.

Generating link…