Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP APM
Known Affected Versions:
10.0.0, 10.0.1, 10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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.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
Fixed In:
12.0.0
Opened: Dec 02, 2014
Severity: 3-Major
In Logon Page agent properties, there is an option "Split domain from full Username". If the option is enabled, then the logon name should be split into username and domain name. However, the agent always used the HTTP POST variable name as a trigger to split variable. It works fine unless administrator renames the POST variable. Then the option does not work as expected
User name is not split and as a result authentication fails.
"Split domain from full Username" enabled and HTTP POST variable "username" is renamed.
As a workaround you can use the Variable Assign agent and split logon name as necessary; then, reassign the two new variables to session.logon.last.username and session.logon.last.domain, respectively.
Now the Logon Page agent uses a session variable name as a trigger. While looping through POST variables, if the associated session variable name is username then the Logon Page agent splits it into username and domain name when the option Split domain from full Username is enabled.
