Bug ID 1083513: BD configuration for botdefense.disable_challenge_failure_reporting gets de-synced with mcpd

Last Modified: May 29, 2024

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

Known Affected Versions:
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

Fixed In:
17.1.1, 16.1.4, 15.1.10

Opened: Feb 25, 2022

Severity: 4-Minor

Symptoms

"Challenge Failure Reason" field in a request event log shows N/A.

Impact

"Challenge Failure Reason" field is disabled.

Conditions

The db key has not been changed manually on the system.

Workaround

Disable the key and re-enable, then save. tmsh modify sys db botdefense.disable_challenge_failure_reporting value disable tmsh modify sys db botdefense.disable_challenge_failure_reporting value enable tmsh save sys config

Fix Information

BD now initialize the db key internally, not depending on mcpd, that ensures the default db key value is "enable".

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips