Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

Hans_Kurppa_159's avatar
Hans_Kurppa_159
Icon for Nimbostratus rankNimbostratus
Jan 19, 2016

VMware Horizon View features with native PCoIP proxy

We have BIG-IP 12.0.0 Build 1.0.628 Hotfix HF1 configured as a native PCoIP proxy without SSL offloading. VMware Horizon View is 6.2.0 build-3005368. APM Access Policy uses two factor SMS authenticat...
application delivery
BIG-IP Access Policy Manager (APM)
Hans_Kurppa_159's avatar
Hans_Kurppa_159
Icon for Nimbostratus rankNimbostratus
Aug 02, 2016

Managed to get it to work. Currently at BIG-IP 12.1.0 and View 6.2.3.

 

https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-third-party-integration-12-1-0/4.htmlconceptid

 

The "Secure tunnel enabled" should probably mention that the setting "Use Secure Tunnel connection to machine" > "External URL" must be the Connection Server's internal name (cs.internal.tld). If it's the actual external URL that Clients use to reach the Horizon View (say vdi.external.tld) the Client connection will not work, as there will be a redirecting issue on the connection.

 

Also, if you need to change the External URL, make sure you create a new SSL certificate with that name and bind it to the Connection Server. If you use the old SSL cert, connections work fine but View Administrator will show the Connection Server as "red" with a SSL cert issue.