Last Modified: Apr 19, 2021
See more info
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.4
Opened: Apr 03, 2018
TMSH/REST API does not filter Username or Client IP for access-info command. The user gives the input as Username or Client IP; still, the tmsh/rest API output does not filter correctly and produces the entire output.
TMSH and REST API command produces more output.
The user gives Username or Client IP for tmsh "show apm access-info" command expecting the filtering will occur based on that given input.
Client Side script in REST API can ignore the empty session in the output and honor the values only when Client IP presents in case of Username as input. Similarly, the script can ignore the values when Username presents in case of Client IP as input.
Filtering should be based on the given input either Username or Client IP based in TMSH and the corresponding REST output.