Tickets :: Comment on [#1317] Inconsistencies between datatree and LDAP when working on a Kolab backend

* Your Email Address
* Spam protection	Enter the letters below: .__ .__ .___..__ .___. [__)[__) \| [__) _/ \| \\| \| \| \./__.
Comment	> Horde allows to login via "mail" or "uid" attribute value in LDAP. > This works fine.However, the queries in the datatree are done based > on the login value of the user. If uid=mail, that doesn't matter, but > having uid=name and mail=name@domain might let the datatree double > the data for the same user. In my case there is the problemthat data > for the user can't be retrieved when he logs in via uid, while > everything works fine when using the mail value. > > There has been a related ticket some days ago, which was about > reading and storing in LDAP. This _is_ solved. This ticket is about > using the same approach in the datatree, i.e. use the value for the > primary LDAP search attribute (Prefs/Prefs/kolab.php sets > $params['uid'] = array('mail', 'uid'); to access the Kolab LDAP > server) for the datatree access (in this example the value of "mail" > and not of "uid").
Attachment
Watch this ticket