Bug ID 969317: "Restrict to Single Client IP" option is ignored for vmware VDI

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 16.1.0, 16.1.1, 16.1.2

Fixed In:
17.0.0, 16.1.2.1, 15.1.4.1, 14.1.4.5

Opened: Dec 03, 2020
Severity: 3-Major

Symptoms

The Restrict to Single Client IP option in the Access Policy is not being honored for VMware VDI.

Impact

A connection from the second client is allowed, but it should not be allowed.

Conditions

- Configure APM Webtop with vmware VDI. - Set "Restrict to Single Client IP" option in Access Profile. - Try to launch vmware desktop on one client. Copy the launch URI - Try to launch vmware desktop from other client using the copied URI.

Workaround

None

Fix Information

Restrict to Single Client IP is honored for VMware VDI for both PCOIP and Blast protocols.

Behavior Change