Bug ID 600488: Automatic addition of legacy PNAgent account in Citrix Receiver

Last Modified: Sep 06, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 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

Opened: Jun 21, 2016
Severity: 3-Major

Symptoms

While using APM in Citrix Storefront integration mode, adding a new account in Citrix Storefront, also adds legacy pnagent account automatically. It is intermittent issue. Issue can be seen while doing logging out from the store, or doing refreshing the apps, or else during reconnecting after closing the Citrix receiver application.

Impact

Citrix receiver is making unnecessary switch between classic and new GUI. Usability becomes the main concern.

Conditions

APM is used as Citrix Storefront integration mode.

Workaround

when HTTP_REQUEST { if { [string tolower [HTTP::uri]] eq "/citrix/pnagent/config.xml" } { log local0. "Received config.xml request, disabling PNAgent access" HTTP::respond 404 } } With this workaround, legacy mode is completely disabled. i.e: Though Store has enabled xenapp services support, APM does not honor it. Note: best practice is to apply the workaround iRule to logoff iRule if applicable

Fix Information

None

Behavior Change