Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.5.0, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Feb 17, 2017 Severity: 4-Minor Related Article:
K85023830
EdgeClient doesn't notify the user when it's time to interact with the logon page.
User may not know that EdgeClient is waiting for the input, hence VPN connection isn't established until user provides credentials
When EdgeClient is minimized to the tray and the page requires user interaction no notification is shown.
In the current Access Policy for each logon-page-and-language combination: * Go to advanced logon page customization. * Open the source code. * Find the following line: 'externalWebHost.webLogonNotifyUser();' * Replace it with the following line: 'externalWebHost.WebLogonNotifyUser();' Note the uppercase 'W' at the beginning of 'WebLogonNotifyUser' replace string.
Now Edge Client correctly notifies the user when it's time to interact with the logon page to perform authentication.