Bug ID 427754: Parameters associated with JSON profile are not enforced after JSON profile is deleted

Last Modified: Nov 22, 2021

Bug Tracker

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

Known Affected Versions:

Fixed In:

Opened: Aug 13, 2013
Severity: 3-Major
Related Article:


Generate the following error in bd.log: ---------------------------------------------------------------------- BD_XML|NOTICE|Jul 18 10:03:38.004|2685|xml_validation.cpp:1309|get from F5XMLProfilesTable obj 0 not found ----------------------------------------------------------------------


These parameters are not enforced.


the JSON profile is deleted and parameter is associated with this json profile.


As a workaround, the violating parameters can be opened for edit, and then saved as User-input parameters. This can be done in the database with the following SQL: ---------------------------------------------------------------------- UPDATE PL_PARAM_ATTRIBUTES param LEFT JOIN PL_PARAM_CONTENT_PROFILES param_cont ON param.id = param_cont.param_attrib_id SET key_input_type = 4, key_ui_type = 32, flg_check_param_value_metachar = 1 WHERE key_input_type = 64 AND param_cont.param_attrib_id IS NULL;

Fix Information

The system prevents a JSON profile from being deleted (even by the Automatic Policy Builder) if there are security policy parameters associated with that JSON profile.

Behavior Change