Bug ID 1135281: Blank LDAP tls_key causes error

Last Modified: May 29, 2024

Affected Product(s):
F5OS None(all modules)

Known Affected Versions:
F5OS-A 1.1.1, F5OS-C 1.3.2

Fixed In:
F5OS-C 1.6.0, F5OS-A 1.3.0

Opened: Aug 09, 2022

Severity: 3-Major


When using the CLI or older webUI, it was possible to enter an "empty" tls_key. This would cause nslcd to be incorrectly configured.


A blank tls_key would fail to work correctly when configuring authentication or talking to the LDAP server.


LDAP configured. Blank LDAP tls_key entered: system aaa authentication ldap tls_key ""


Explicitly set the bind password to unset: no system aaa authentication ldap tls_key

Fix Information

Fixed authentication so any form of "empty" tls_key results in the tls_key being unset.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips