I'll try to reformulate my question:In my understanding, OST ldap plugin always uses user/passwd (if specified) for binding to the LDAP sever. Only if user/passwd is not specified, the plugin will try to do an anonymous bind.I have an OST 1.9.12 with LDAP plugin v0.6.2, up and running fine against a server LDAP (this ldap server accepts anonymous bind). I've an username and passwd specified in the ldap plugin config, so I supposed that ldap uses that user and password to do the BIND operation.Now I need to improve my LDAP server security configuration and DISALLOW accepting anonymous bind. When I change my ldap server config, adding the sentence "disallow bind_anon", logging to OST via ldap stops working, and I get the next ldap server log error message:Nov 5 12 mufrid2 slapd: conn=20771 op=1 STARTTLS
Nov 5 12 mufrid2 slapd: conn=20771 op=1 RESULT oid= err=0
text=
Nov 5 12 mufrid2 slapd: conn=20771 fd=32 TLS established
tls_ssf=256 ssf=256
Nov 5 12 mufrid2 slapd: conn=20771 op=2 BIND dn="" method=128
Nov 5 12 mufrid2 slapd: conn=20771 op=2 RESULT tag=97
err=48 text=anonymous bind disallowed
Nov 5 12 mufrid2 slapd: conn=20771 op=3 UNBIND
Nov 5 12 mufrid2 slapd: conn=20771 fd=32 closed Why it's trying to do ANONYMOUS BIND, despite having user/passwd in the config?Any idea of what's going on?Thanks a lot again!!Cesc