Bug ID 485202: LDAP agent does not escape '=' character in LDAP DN

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.5.1, 11.5.1 hf1, 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.1 hf10, 11.5.1 hf11, 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.5.10, 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: Oct 17, 2014

Severity: 4-Minor

Symptoms

Starting from BIG-IP 11.6.0, session variables may have modifiers when used in configuration, such as: %{session.logon.last.ldap.dn:ldapdn} With session variable modifier "ldapdn", the resultant value should be escaped by LDAP DN rules. The rules include an equals (=) character which should be escaped, but it is not.

Impact

Depends on the purpose of usage session variable with "ldapdn" modifier in a configuration.

Conditions

LDAP session variable that contains LDAP DN is used in configuration with "ldapdn" session variable modifier.

Workaround

It is possible to escape '=' character using the Variable Assign agent before using that session variable with the modifier in other configurations.

Fix Information

Now the session variable modifier "ldapdn" escapes the equal sign (=) character as well as other characters that require escaping.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips