Bug ID 512687: Policy parameter fields minimumValue and maximumValue do not accept decimal values through REST but accept decimal through GUI

Last Modified: Apr 10, 2019

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.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, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0, 11.5.3

Opened: Mar 16, 2015
Severity: 4-Minor

Symptoms

Create security policy named "policy1" Send POST to -------------------------- https://<BIG-IP>/mgmt/tm/asm/policies/<asm-policy-uuid>/parameters -------------------------- with body: -------------------------- { "name": "decimal", "dataType": "decimal", "maximumValue": 20.1 } -------------------------- you will get error saying: -------------------------- "Could not parse/validate the Parameter. Field value for maximumValue must be an integer." --------------------------

Impact

Not able to create a decimal parameter with floating "minimumValue" and "maximumValue" properties using REST API.

Conditions

ASM is provisioned.

Workaround

None.

Fix Information

It is now possible to create a decimal parameter with floating "minimumValue" and "maximumValue" properties using REST API.

Behavior Change