Bug ID 2256705: Re-importing BIG-IP LTM device into BIG-IQ fails with "not authenticated" error when log-config filter/publisher objects are out of sync

Last Modified: Jul 28, 2026

Affected Product(s):
BIG-IQ ADC(all modules)

Fixed In:
8.4.2

Opened: Mar 23, 2026

Severity: 3-Major

Symptoms

When attempting to re-import a BIG-IP LTM device into BIG-IQ, the operation fails during the COPY_CONFIG step with the following error: Failed to copy configuration to working-config; reason: Failed copying from source to target: java.lang.RuntimeException: not authenticated The failure occurs during bulk update operations involving log-config filter and publisher objects.

Impact

Users are unable to re-import BIG-IP LTM devices into BIG-IQ when log-config filter/publisher objects are out of sync. This blocks configuration management and synchronization between BIG-IQ and BIG-IP devices.

Conditions

-- Log-config publisher objects exist on both BIG-IPs -- Log-config filter object exists only on one BIG-IP -- After modifying the log-config filter on the BIG-IP with the filter, and re-importing into BIG-IQ, a sync gap is created -- Re-import triggers a bulk update, targeting the device missing the filter

Workaround

None.

Fix Information

Re-importing BIG-IP LTM devices now succeeds even when log-config filter/publisher objects are out of sync. The "not authenticated" error no longer occurs.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips