[Tickets #7418] Re: Unable to write filters to prefs with ldap backend (binds without password)

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/7418
------------------------------------------------------------------------------
  Ticket             | 7418
  Updated By         | m.rolke at linux-ag.com
  Summary            | Unable to write filters to prefs with ldap backend
                     | (binds without password)
  Queue              | Ingo
  Version            | 1.2.1
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


m.rolke at linux-ag.com (2009-04-17 10:49) wrote:

I can confirm this bug, too.
The users password is needed when the option
         $conf['prefs']['params']['writedn']
in the horde conf.php is set to 'user'.

Adding the users password as the fourth argument in the "$prefs =  
&Prefs::singleton" call fixed this issue for me. Thank you urkle for  
this tip (Comment #3)!

Sadly, this bug appears not only in ingo but in kronolith and some  
other horde apps, too.
I did a quick search in my horde directory and found many other calls  
to the Prefs::singleton function, where the password argument is an  
empty string.

So, is there a reason why applications should not pass the users  
passwort to the singleton function?
I would prefer the method of writing preferences to the LDAP as the  
logged-in user instead of writing as admin.

Thank you in advance!