Last Modified: Apr 17, 2024
Affected Product(s):
BIG-IP APM
Known Affected Versions:
14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2
Opened: Feb 06, 2020 Severity: 3-Major
APM has three primary types of session variables: - Per-Session Variables - Per-Flow Variables - Subsession Variables If you attempt to use a per-flow variables (perflow.*) inside of an AAA agent in a subroutine, the resultant variable will appear to be blank, when it should have a value.
The APM administrator will be unable to use perflow variables in AAA agents in a per-flow policy subsession macro.
Usage of perflow.* variables inside some AAA agents such as AD Query/Auth and LDAP Query/Auth inside of a per-request subroutine.
To work around this problem, use a Variable Assignment agent to set a subsession variable immediately before the AAA agent, and then configure the AAA agent to use the subsession variable. For example: [Variable Assign Agent] [custom variable]subsession.custom = [session variable]perflow.custom
None