Problems getting LDAP authentication working

[ctxis]

Problems getting LDAP authentication working

[sadreck]

I've added an option to select between "Simple" and "NTLM" under the settings.

I'll close the issue now, but if something isn't working feel free to open it again.

[sadreck]

Hi,

1. Just to confirm, is your LDAP SSL running on port 636? You can check by connecting using ldp.exe on the AD itself by setting the port to 636.
2. From the sounds of it something is going on with the user you are trying to bind with. In my test environment this is what the format/config looks like (domain is marvel.local):
   

I've added a feature in the settings (under LDAP) that will allow you to test the connection and get a (hopefully) meaningful error message. Pull the latest and greatest and give it another go!

Thanks,
Pavel

[tautology0]

The problem with connecting to LDAPS appears to be due to channel binding tokens - i.e. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters\LdapEnforceChannelBinding is set to 2. This is because crackerjack is connecting to LDAP via NTLM rather than through kerberos.

[tautology0]

One of my colleagues offered a suggestion which fixed this with a simple change on line 209 of app/lib/base/ldap.py; by changing authentication from ldap3.NTLM to ldap3.SIMPLE. (Sorry I can't easily do a pull request from here):

connection = ldap3.Connection(server, user=ldap_user, password=password, authentication=ldap3.SIMPLE)

Obviously this is not sensible to do over unencrypted LDAP, so it may be worth doing some simple logic chose the authentication method.