Re: Raw backtrace multiple passwords not allowed

2016-07-10 Thread Leon Kyneur
You sure you're not returning multiple password attributes from LDAP? Aki pass_attrs = 'mail=user, userPlaintextPassword=password_noscheme, =proxy=y, =pass=%{ldap:userPlaintextPassword}, =host=%{ldap:mailstoreHost}' I am returning the same password attribute into different fields :

Re: Raw backtrace multiple passwords not allowed

2016-07-10 Thread aki . tuomi
You sure you're not returning multiple password attributes from LDAP? Aki > On July 10, 2016 at 1:32 PM Leon Kyneur wrote: > > > This turned into quite a large problem for me but think I have resolved it. > > After toying this a few settings I ended up (out of sheer desperation)

Re: Raw backtrace multiple passwords not allowed

2016-07-10 Thread Leon Kyneur
This turned into quite a large problem for me but think I have resolved it. After toying this a few settings I ended up (out of sheer desperation) setting "blocking = yes" in my LDAP configuration. Is this a logical thing to do? I couldn't find much on it other than i'm guessing queries are no

Raw backtrace multiple passwords not allowed

2016-07-09 Thread Leon Kyneur
Hi Recently enabled support for encrypted passwords on my proxies - CRAM-MD5, DIGEST-MD5, NTLM and APOP to support some new users. Most users are working perfectly though every so often I see this happening in the logs: Jul 09 06:32:51 auth: Error: ldap(u...@domain.com,192.168.10.90,):