Bug ID 603081: EdgeClient now supports hosts whitelisting in locked mode

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Jul 06, 2016

Severity: 3-Major

Symptoms

Edge client's locked mode blocks access to all network locations until the user establishes a VPN connection to a trusted APM. However, this does not work when APM is configured to use delegated auth because access to external identity provider (IdP) is blocked.

Impact

No way to whitelist certain hosts when locked client mode is used.

Conditions

EdgeClient in locked mode on windows machine.

Workaround

None.

Fix Information

The system now supports pre-configured hosts to which the traffic is never blocked until VPN is established, so you can whitelist known identity providers (IdPs) and other sites that are deemed harmless, which improves the usability of locked client mode. After VPN establishment client behaves according to Network Access resource configuration.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips