Hi guys, I am experiencing some erratic behavior getting koha to talk to our ldap server. I am trying setup where koha updates existing user details (mainly passwords) but not replicate. This way only users created on the koha server are able to authenticate since the userid on koha is the same as on our ldap(openldap). However my experience has been very inconsistent. Users are not immediately authenticated until after numerous tries (and restarting koha-common) and when a user is eventually authenticated changes to the user password on ldap are not immediately reflected. Here are my system details koha 3.12 using debian Squeeze Packages here is my ldap configuration. <useldapserver>1</useldapserver><!-- see C4::Auth_with_ldap for extra configs you must add if you want to turn this on --> <ldapserver id="ldapserver" listenref="ldapserver"> <hostname>192.168.0.1</hostname> <base>ou=People,dc=example,dc=com</base> <user>admin,ou=People,dc=example,dc=com</user> <pass>password</pass> <replicate>0</replicate> <update>1</update> <mapping> <userid is="uid"></userid> <surname is="sn"></surname> <password is="userPassword"></password> </mapping> </ldapserver> I have been able to get other services like pam (library desktops running Linux) moodle, and alfresco to authenticate users against our ldap. If anyone could point me to with I am doing wrong and if there is any other switch which need be flipped to get ldap working on Koha I would really appreciate. Also any means of getting a more verbose log on what happens when koha tries to authenticate against ldap.. I have not be able get any log on whats from from opac.err intranet.err.