Bug ID 754865: Missing indication when client fails connecting to Security Cloud Services

Last Modified: Sep 27, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1

Fixed In:
15.0.0

Opened: Jan 08, 2019
Severity: 4-Minor

Symptoms

When Security Cloud Services and Centralized Device ID are enabled, the clients may be blocked from accessing the site if there is no connectivity to the Cloud Services. There is no indication of these failures.

Impact

Connectivity fails with no indication of the failure. Administrators cannot monitor users getting blocked due to connectivity failures with the Cloud Services.

Conditions

-- Security Cloud Services are enabled. -- Centralized Device ID is enabled. -- Device ID is enabled on a Bot Defense profile. -- There is no connectivity between clients and the Cloud Services.

Workaround

None.

Fix Information

There is now an indication in the Bot Defense Request Log when clients are blocked due to 'Cloud connectivity failure'. This appears in the 'Challenge Failure Reason' field.

Behavior Change