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

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1317
-----------------------------------------------------------------------
 Ticket     | 1317
 Created By | a.gungl at gmx.de
 Summary    | Inconsitences between datatree and LDAP when working on a Kolab backend
 Queue      | Horde Framework Packages
 State      | Unconfirmed
 Priority   | 3. High
 Type       | Bug
 Owners     | 
-----------------------------------------------------------------------


a.gungl at gmx.de (2005-02-07 05:36) wrote:

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 at 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").