GrumbleDook (16th July 2008), zag (17th July 2008)
I'm still struggling to try and authenticate users using LDAP in moodle. I keep getting this error when trying to log in as a teacher
Here's my config, any ideas whats wrong? I'm guessing it cant login to the ldap server but no idea how to fix as all the credentials seem correct and I can login using ldap.exe with the usernameI've created a new user with admin rights called ldap-user.
![]()
Is the path correct for the OU that ldap-user is in?
Seems like there's a fairly low level connection issue here. There is a thread here on the error which might be helpful: http://moodle.org/mod/forum/discuss.php?d=71186
The error seems to be a bind problem so that would suggest your distinguishing name or password is wrong....?
Cheers
Jona
distringuised name needs to be properly populated, for example
cn=moodle,ou=system logons,ou=Schoolname,dc=curriculum,dc=local
cn being the username, ou being the ou's (bottom one first), dc being domain name and domain extension.
the context should look like this
ou=schoolname,dc=curriculum,dc=local
this should be the toplevel ou where your subjects are contrained.
EDIT: nevermind worked it out
in the distringuised name I put the users email address.
and in the context i putCode:ldap-user@domain.sch.uk
Thanks for all the help, all the replies helped me find the solutionCode:ou=InterJigsaw,dc=domain,dc=domain 2nd bit,dc=sch,dc=uk![]()
Last edited by zag; 16th July 2008 at 03:47 PM.

For anyone else struggling with LDAP type problems, I recommend downloading LDAP browser from softterra Softerra LDAP Administrator & Browser: Directory Management Tool Download it lets you browse your active directory using LDAP so you get the view and structure that LDAP programs will see, and the best bit is if you need an LDAP indetification string to address an object, you can copy and paste it out of the program directly into moodle or simelar. Saves a bit of time in writing them yourself and makes sure they're correct!
Mike.
GrumbleDook (16th July 2008), zag (17th July 2008)
Yep thats exactly how I solved my problem, the ldap strings can be confusing to say the least!
There are currently 1 users browsing this thread. (0 members and 1 guests)