The bindDn and the bindpasswoard are required if :
1) your LDAP doesn t accept anonymous request (you can add an ACL to accept anonymous request from the 127.0.0.1) in this case the DN should be found.
2) Tte DN must be searched if you have a multi level LDAP organisation (example with some ou or o )
in this case the auth make a first search to search the dn and after bind with this DN.
Regards
Alain
Le Mardi 13 Août 2013 04:00 CEST, "(HT) Simon Walter" <[email protected]> a écrit:
On 08/13/2013 10:15 AM, (HT) Simon Walter wrote:
> Is it possible to provide the hash value here? Would not that be safer
> than storing the password in clear text?
>
> Any additional information into this parameter with regards to
> security and how others are using it would be most welco me.
>
Perhaps, I'll end up answering my own question. Though I'd still like to
be sure that this is the case.
If I use bindAsCurrentUser, it seems apparent that bindDN and
bindPassword is not required. Is that the case? "If bindFields is set,
bindDN and bindPassword will still be required to find the proper DN of
the user." Does that mean if my LDAP schema is non-standard(objectClass:
person(?)) that I'll have to use bindFields and therefore require a
bindDN? (I'm guessing uid and userPassword are what SOGo expects to
exist by default.)
Are there any other cases in which bindDN and bindPassword are required?
Thanks,
Simon
--
[email protected]
https://inverse.ca/sogo/lists
