3.1 Released On 19 Sep 2017 and 3.1.1 Released on 27 Oct 2017
These release notes include the following topics:
- What's New in 3.1.1 Release
- Resolved Issues in 3.1.1 Release
- Miscellaneous Updates in 3.1.1 Release
- What's New in 3.1 Release
- Compatibility Notes
- Known Issues in 3.1
The latest release of Unified Access Gateway 3.1.1 includes many updates and important bug fixes for issues found in previous releases of Unified Access Gateway.
- BSG updated to fix UDP forwarder crash.
- Unified Access Gateway unresponsive after thread synchronization.
- Static routes had stopped working.
- Missing JSON property config under the Device Policy Check tab in Admin UI.
- Connectivity issues to API/AWCM in Unified Access Gateway 3.0
- API call issues in Content Gateway when using Outbound proxy.
- Improved UI terminology and error messages for host entries.
- SLES 12 SP2 updated to latest patch level.
- Improved UI for SAML Identity Provider and Service Provider screens.
- Updated JRE version to 8u151.
VMware Unified Access Gateway™ 3.1 provides the following new features and enhancements.
- Identity Bridging - Certificate-to-Kerberos
Support for Identity bridging using Kerberos Constrained Delegation (KCD). End-users using mobile devices can access web applications that require Kerberos authentication using a client certificate.
- Endpoint Compliance Check
Provides additional security to check if the connecting client endpoint device conforms to the customer's defined policy. This feature is currently supported for Horizon use case.
- Integration with Horizon Helpdesk
You can monitor Unified Access Gateway from Horizon Helpdesk for easy troubleshooting.
- Admin UI Enhancements
Several new enhancements have been made to the Admin UI to ease deployment. You can validate additional certificate formats, export INI files, view NIC configuration, and view troubleshooting information.
- AirWatch Content Gateway Integration as a Service
Unified Access Gateway now supports AirWatch Content Gateway services in addition to AirWatch Tunnel.
- Support for Microsoft Azure Deployment
Unified Access Gateway can now be used in Microsoft Azure tenant environment for VMware Horizon deployments.
The Unified Access Gateway user interface, online help, and product documentation are available in Japanese, French, German, Spanish, Brazilian Portuguese, Simplified Chinese, Traditional Chinese, and Korean. For the complete documentation, see the Documentation Center for VMware Unified Access Gateway.
For more information about the VMware Product Interoperability Matrix, see http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Smart card authentication does not work while connecting to the Unified Access Gateway server if the alternate subject name has the email address for the certificate mapped with the domain account.
Workaround: In the wizard for creating a certificate template for the smart card user, on the Subject Name tab, deselect the checkbox "Include this information in alternate subject name:".
Unified Access Gateway session timeout does not disconnect the Blast Connection.
Workaround:Keep the session timeout on UAG greater than or equal to that of Horizon server.
- An authentication setting that is enabled cannot be disabled from the Admin UI. This is true for all the authentication settings.
Note - An authentication setting is not used until it is applied in an edge service.
Workaround: If an authentication setting is not needed in an edge service setting, follow the steps below to disable the setting:
- Click the gear icon next to that edge service setting. A pop-up window is opened.
- Locate the label Auth Methods and select the option Select Auth from the drop-down menu.
- Click Save.