Last Modified: Sep 13, 2023
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 126.96.36.199, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11
14.0.0, 18.104.22.168, 13.0.1, 22.214.171.124, 11.6.3
Opened: Sep 30, 2017 Severity: 3-Major
Current logic for determining whether to offer HTML5 client option works for Horizon 6.x (and earlier) but it does not work for Horizon 7.x. With Horizon 7.x, VMware has enhanced the XML so that each resource includes a flag to indicate whether HTML5 client is enabled (absence of <html-access-disabled/> tag). APM does not honor this flag to show HTML5 client option to APM end user only if it has been enabled for that resource.
APM offers HTML5 client launch option and actually runs it if requested, although it is disabled at the backend.
-- APM webtop with a VMware View resource assigned. -- HTML5 Access disabled for some of the RDS farms managed by the broker.
There is no workaround at this time.
For Horizon 7.x, the system now honors the <html5-access-disabled> flag in broker responses to disable HTML5 client for those RDS desktops and apps that have this flag set.
Before this fix, all the RDS desktops and apps were available for HTML5 client if it was installed on VCS. Now, for those desktops and apps where HTML5 access has been deliberately disabled at the broker, only the native client option will be available.