Bug ID 709319: Post-login client-side alerts are missing username in bigIQ

Last Modified: Sep 14, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 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, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6

Fixed In:
14.0.0, 13.1.0.6

Opened: Mar 08, 2018

Severity: 3-Major

Symptoms

A client-side alert that contains a FPS-Username header with a value, but an empty fpm_username parameter - will be reported with "Unknown" username in bigIQ.

Impact

Post login client side alerts are missing username (will show as "Unknown" in bigIQ, works well with Alert-Server).

Conditions

1. post login (alert is sent after submitting username parameter) client side alerts 2. alert-pool points to bigIQ IP (not Alert-Server)

Workaround

Route all client-side alerts to another virtual server and strip of the empty fpm_username parameter from payload/query-string.

Fix Information

FPS will always send username in the fpm_username parameter in case it was empty and FPS has username value.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips