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

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3,,,,, 11.6.4, 11.6.5,,,

Fixed In:

Opened: Feb 24, 2015
Severity: 3-Major
Related Article:


Access Policy with multiple logon pages logs a blank username.


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).


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



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