Bug ID 544831: ASM REST: PATCH to custom signature set's attackTypeReference are ignored

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2

Fixed In:
12.1.0, 11.5.4

Opened: Sep 09, 2015
Severity: 3-Major

Symptoms

When trying to update filter/attackTypeReference for a User-Defined Filter-Based Signature Set (/mgmt/tm/asm/signature-set/<ID>), the PATCH call completes successfully, but the change never occurred.

Impact

The PATCH call completes successfully, but the change never occurred. This may result in the Signature Set not containing the expected signatures.

Conditions

Using the REST API, a user tries to update filter/attackTypeReference for a User-Defined Filter-Based Signature Set (/mgmt/tm/asm/signature-set/<ID>)

Workaround

The bug only exists via the REST API, the GUI can be used to change this value.

Fix Information

The attackTypeReference field is now correctly updated using a REST PATCH.

Behavior Change