Last Modified: May 27, 2020
See more info
Known Affected Versions:
14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.0.1, 220.127.116.11, 15.0.0, 15.0.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 15.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Feb 06, 2020
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