Bug ID 671138: FireFox and Chrome users are asked to re-install windows "Endpoint Inspector Application" after upgrade from 13.0.0

Last Modified: Nov 15, 2019

Bug Tracker

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2

Fixed In:
13.0.1

Opened: Jun 26, 2017
Severity: 3-Major

Symptoms

After upgrade from 13.0.0 to 13.1.0, or a later release, all APM end users running FireFox and Chrome browsers on Microsoft Windows are asked to re-install 'Endpoint Inspector Application'. The following page appears: 'Browser is waiting for status from Endpoint Inspector Application.' 'Please confirm that this application is launched and is not waiting for your input. This application may be behind other windows on your desktop.' Link and installation instructions provided behind 'More Option' link.

Impact

APM end users are prompted to install the endpoint inspector application.

Conditions

Endpoint inspection configured in BIG-IP APM access policy.

Workaround

No workaround. APM end users must follow instructions to install application. Note: When 'Endpoint Inspector Application' is not installed, the instruction screen is clearly visible, as it is part of normal APM usage. However, when 'Endpoint Inspector Application' is installed, the instructions window is hidden behind the 'More Option' link, and the APM end users must click the link to view the instructions.

Fix Information

Previously, APM end users running FireFox or Chrome browsers on Microsoft Windows were asked to re-install the Endpoint Inspector Application after upgrading. The issue is resolved for upgrades from 13.1.0 to newer releases. Note: The specific upgrade path from 13.0.0 to 13.1.0 cannot be fixed, so the issue will still occur in that particular case.

Behavior Change