Bug ID 555006: ASM REST: lastUpdateMicros is not updated when changing a Custom Signature

Last Modified: Oct 10, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, BIG-IQ(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, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4

Opened: Oct 29, 2015
Severity: 2-Critical

Symptoms

The lastUpdateMicros field is meant to be updated if a user changes a custom signature, but it is not.

Impact

Checking for updated signatures does not return the expected result.

Conditions

REST client is used to look at/filter the signatures collection (/mgmt/tm/asm/sigantures)

Workaround

None.

Fix Information

REST: The lastUpdateMicros field is now correctly updated after updating a user defined signature.

Behavior Change