Bug ID 508767: Access Policy with multiple logon pages log a blank username

Last Modified: May 29, 2024

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

Known Affected Versions:
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.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0

Opened: Feb 24, 2015

Severity: 3-Major

Related Article: K04732437

Symptoms

Access Policy with multiple logon pages logs a blank username.

Impact

Exporting reports in CSV format from Access Policy > Reports > View Reports might contain break (<br/>) tags, and the logs report Username ' ' (that is, a blank username).

Conditions

Configure an access policy using visual policy editor with multiple logon pages. On the second logon page, specify Username as Readonly.

Workaround

None

Fix Information

When the Logon Page configuration specifies that the username field is Read Only, APM no longer logs the username, which is always empty in this case. When the Logon Page configuration requires the user to enter a username, APM continues to log the username.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips