Re: [SOGo] Sogo nightly - LDAP authentication doesn't work

I've updated to latest nightly build and inserted the key "bindFields"
as described,
but unfortunately still the same result:

May  8 22:29:16 srv1 slapd[1699]: conn=1012 fd=21 ACCEPT from
IP=127.0.0.1:59681 (IP=0.0.0.0:389)
May  8 22:29:16 srv1 slapd[1699]: conn=1012 op=0 BIND
dn="uid=aschlager,ou=users,dc=daheim,dc=at" method=128
May  8 22:29:16 srv1 slapd[1699]: conn=1012 op=0 RESULT tag=97 err=49 text=
May  8 22:29:16 srv1 slapd[1699]: conn=1012 op=1 UNBIND
May  8 22:29:16 srv1 slapd[1699]: conn=1012 fd=21 closed

Am 2012-05-08 20:25, schrieb Ludovic Marcotte:
> On 05/05/12 21:33, Jean Raby wrote:
>> Alright, SOGo is not doing an indirect bind, it tries to bind
>> directly as uid=username,baseDN.
>>
>> From a quick look at the code, it seem that you need to set
>> 'bindFields' to tell it to do the inderect bind.
>>
>> Can you try adding this to you user source:
>> <key>bindFields</key>
>> <array>
>> <string>uid</string>
>> </array> 
> This is indeed the case.
>
> If you use an indirect bind (so you have defined bindFields), SOGo
> will use the bindDN to lookup the DN of the user. If found, it'll then
> try to bind using it.
>
> If you don't use bindFields, SOGo will generate the proper DN based on
> your SOGoUserSources' entry configuration and bind using it.
>
> In both cases, SOGo will cache the DN of the user for subsequent
> calls. It caches it internally, not in memcached. So if you want to
> completely flush that data, you must restart SOGo.
>