Bug ID 725840: Customization group object is not deleted when SAML resource object is deleted

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Fixed In:
14.1.0

Opened: Jun 27, 2018
Severity: 3-Major

Symptoms

Customization group object for the corresponding SAMLResource object is in the configuration store, even after SAMLResource is deleted in GUI/TMSH.

Impact

There is no functional impact, but additional configuration objects exist in the configuration store.

Conditions

-- Customization Object is in the configuration store. -- Delete the SAMLResource.

Workaround

Delete the customization group object manually in TMSH. The BIG-IP system administrator can delete those customization groups if the corresponding SAML resources are deleted or do not exist in the configuration. The command 'list apm policy customization-group' lists all the customization groups. The SAML-specific customization groups end with '_resource_saml_customization' and are prefixed with the SAML resource name (SAML resource name concatenated with literal 'resource_saml_customization').

Fix Information

Customization group objects are now deleted when the SAML Resource object is deleted.

Behavior Change