Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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
Fixed In:
13.0.0
Opened: Nov 16, 2016 Severity: 3-Major Related Article:
K02559435
Certain policies or macros can't be edited properly, usually after import. Errors like "Agent (XYZ) is already referenced by another access policy item" or "Access policy item type Action (XYZ) is already referenced by more than one access policy item."
VPE is unable to add action / create agent of certain types.
When adding new item in certain (usually imported) policies where situation like %PROFILE%_logon_page_1 uses %PROFLE%_logon_page_2_ag might end up that %PROFILE%_logon_page_2 wouldn't be able to create agent
Editing bigip.conf and restoring enumeration for offending item (better for item rather than agent) would help to avoid this bug
VPE now properly checks for existing agent names, so policies or macros can be edited properly.