[Tickets #1786] LDAP Preferences - Wrong bind DN

[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=1786
-----------------------------------------------------------------------
 Ticket             | 1786
 Updated By         | ben.sommer at enc.edu
 Summary            | LDAP Preferences - Wrong bind DN
 Queue              | Horde Framework Packages
 State              | New
 Priority           | 2. Medium
 Type               | Enhancement
 Owners             | 
+New Attachment     | config-conf.xml.diff
-----------------------------------------------------------------------


ben.sommer at enc.edu (2005-04-18 11:52) wrote:

Here's my proposed solution to this problem:

Horde's Prefs ldap driver requires either
    A) a root DN and password to search for and modify a user's prefs 
fields, or
    B) a simple-to-concatenate user DN formula (such 
$conf['prefs']['params']['uid'] + a $base_dn)

A) is a problem because root binds to an LDAP server are neither 
necessary nor desired to do most any user-level write operations.
B) is a problem because my (like the original poster's) person schema does
not conform to such a simplistic formula. DNs look like this:

    ueid=84kjasd99,ou=8,ou=people,dc=enc,dc=edu

The solution is to make the Prefs ldap driver behave like most LDAP apps 
that need to do write operations: do an anonymous bind, search for the 
entry to modify using a filter, then rebind as the DN of that entry and 
do the write.

This is a config issue, and horde admins should be aware of the option. To
this end, I added an option under LDAP-config Preferences in conf.xml.