Page 1 of 1

[SOLVED] Djoin problem since WAPT 2.4 update

Published: June 22, 2023 - 4:31 PM
by erems
Hello,

we upgraded WAPT today from 2.3 to 2.4.0.14080 on a Linux Ubuntu 20.04.6 server.

The djoin functionality has changed, and we can no longer get it to work with our Samba Active Directory. The WAPT 2.4 documentation doesn't seem to be up-to-date on this point.

I consistently get a "TLdapClient.Bind with a password requires TLS connection" error, regardless of the port used (389, 636, etc.).

A tcpdump on the WAPT server doesn't show any outgoing requests to the domain controller when I prepare the djoin. This doesn't seem normal.

Until now, the options used were equivalent to those described in the documentation.

Picture

Could you please help us?

Best regards.

Re: Djoin problem since the WAPT 2.4 update

Published: June 22, 2023 - 5:48 PM
by sfonteneau
Hello

, could you please provide your version of Samba so we can run some tests?

Simon

Re: Djoin problem since the WAPT 2.4 update

Published: June 23, 2023 - 09:14
by erems
Hello,

The DCs use Samba 4.15.13

Regards.

[SOLVED] Re: Djoin problem since WAPT 2.4 update

Published: June 23, 2023 - 11:34
by sfonteneau
I just tried

Samba 4.15 (KO)
and Samba 4.16.10 (OK).

In the 4.16 changelog, we can see:

* BUG 14996: Fix ldap simple bind with TLS auditing.

I believe this bug from the older versions is causing the problem.

Since Samba 4.15 has been end-of-life since March 8, 2023:

https://wiki.samba.org/index.php/Samba_Release_Planning,

I therefore suggest you upgrade to restore normal operation. ;)

Simon

Re: Djoin problem since the WAPT 2.4 update

Published: June 23, 2023 - 11:53
by erems
Hello,

thank you for your reply, that explains this behavior.

Best regards.