Hmm... Were you getting 'lak_bind() fail' messages in the (auth) syslog? Did you specify ldap_auth_method in saslauthd.conf?
-Igor On Wed, 23 Oct 2002, Kervin L. Pierre wrote: > ok. > > well something else caused saslauthd to lose its connection to start > searching as anonymous. I'm sure I did not change the configuration, > and restarting saslauthd fixed the problem. > > --Kervin > > Igor Brezac wrote: > > On Wed, 23 Oct 2002, Kervin L. Pierre wrote: > > > > > >>If the ldap server goes offline temporarily, and saslauthd binds with a > >>special user, when the ldap server gets back online, saslauthd tries to > >>use anonymous instead of the priviledged user. > > > > > > No. "anonymous" in the code means whatever you passed as lak_bind_dn. > > > > > >>Or so it looks like on my machine. > >> > >>So I guess whenever the ldap server is restarted saslauthd will need to > >>be restarted as well? > >> > > > > > > You do not need to restart saslauthd. saslauthd will reconnect when the > > ldap server(s) comes back online. I tested this quite extensively with > > both auth methods. > > > > -Igor > > > > > -- Igor
