Bug ID 675554: No validation for domain and domain-controller in Active Directory server

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jul 25, 2017

Severity: 3-Major

Symptoms

There is no error given when an invalid domain or domain-controller in Active Directory (AD) server is configured via tmsh and iControl.

Impact

Failure occurs when the configuration is used by data traffic.

Conditions

Configure AD with an invalid domain and domain-controller, e.g.: tmsh create apm aaa active-directory ad-temp-02 { domain aaa$%^&aaa domain-controller test.%% }

Workaround

You can use either of the following workarounds: -- Configure using the GUI, which has validation. -- Configure with care via tmsh and iControl.

Fix Information

The system now reports an error when an invalid domain or domain-controller of AD server are provided during configuration via tmsh or iControl.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips