LDAP not working
Posted: 10 Aug 2014, 06:33
I cannot for the life of me get LDAP to work. I have successfully configured other programs to use my LDAP server, but in this case, I don't even think Madsonic is even trying to communicate with the server. Running the latest 5.1.4800.beta2 on an MINT 17 linux server, but I couldn't get this to work in previous releases either.
I have configured LDAP following many of the different online examples. The LDAP server is a dirsrv server which is part of a Kolab installation (http://www.kolab.org). I have the following settings which are customized for the Kolab LDAP server:
LDAP URL: ldap://mail.example.org:389/ou=people,dc=example,dc=org
LDAP search filter: (uid={0}) <- I don't know if this is right for the Kolab schema
LDAP manager DN: uid=kolab-service,ou=Special Users,dc=example,dc=org
Password has been entered, but it appears blank on screen; however I see an encrypted password in the madsonic.properties file. LDAP enabled checkbox is checked, as well as the auto create one.
The reason I don't think this is even trying to talk to my LDAP server is that I have a tcpdump running on the madsonic server, using the LDAP server IP and port 389 as the filter. If I try to log in with a LDAP user that is not in the madsonic database, I instantly get returned to the login screen. The tcpdump count remains at zero.
I know the tcpdump is working because if I run an ldapsearch query on the madsonic server from the command line, the tcpdump counter goes up by 14.
I've also noticed that the authenticate user with LDAP box doesn't stick when modifying users. However, if I modify that flag directly in the database, that user cannot log in and the tcpdump count doesn't increase.
So before I can even troubleshoot any possible authentication and/or lookup issues, I need to get Madsonic to try to talk to LDAP server before I can do that.
I have configured LDAP following many of the different online examples. The LDAP server is a dirsrv server which is part of a Kolab installation (http://www.kolab.org). I have the following settings which are customized for the Kolab LDAP server:
LDAP URL: ldap://mail.example.org:389/ou=people,dc=example,dc=org
LDAP search filter: (uid={0}) <- I don't know if this is right for the Kolab schema
LDAP manager DN: uid=kolab-service,ou=Special Users,dc=example,dc=org
Password has been entered, but it appears blank on screen; however I see an encrypted password in the madsonic.properties file. LDAP enabled checkbox is checked, as well as the auto create one.
The reason I don't think this is even trying to talk to my LDAP server is that I have a tcpdump running on the madsonic server, using the LDAP server IP and port 389 as the filter. If I try to log in with a LDAP user that is not in the madsonic database, I instantly get returned to the login screen. The tcpdump count remains at zero.
I know the tcpdump is working because if I run an ldapsearch query on the madsonic server from the command line, the tcpdump counter goes up by 14.
I've also noticed that the authenticate user with LDAP box doesn't stick when modifying users. However, if I modify that flag directly in the database, that user cannot log in and the tcpdump count doesn't increase.
So before I can even troubleshoot any possible authentication and/or lookup issues, I need to get Madsonic to try to talk to LDAP server before I can do that.