<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>LDAP Prefs backend, kronolith tries to bind w/o password</title> 
  <pubDate>Fri, 10 Apr 2026 17:02:34 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8246</link> 
  <atom:link rel="self" type="application/rss+xml" title="LDAP Prefs backend, kronolith tries to bind w/o password" href="https://bugs.horde.org/ticket/8246/rss" /> 
  <description>LDAP Prefs backend, kronolith tries to bind w/o password</description> 
 
   
   
  <item> 
   <title>Similar issue to http://bugs.horde.org/ticket/7418 in Ingo -</title> 
   <description>Similar issue to http://bugs.horde.org/ticket/7418 in Ingo - tries to bind to LDAP as user without password. 



System is using LDAP for preferences. The first time after logging on to the Horde system, saving a new event in Kronolith generates the error message in the attached screenshot. The event saves correctly and is written to SQL as needed. The issue appears to be cosmetic only. Once the error has been thrown, subsequent event saves do NOT produce the error until after a logout / login.



LDAP logs show:



May  6 18:25:18 server01 slapd[1156]: conn=73358 op=2 BIND dn=&quot;uid=simon,ou=users,dc=simonandkate,dc=lan&quot; method=128

May  6 18:25:18 server01 slapd[1156]: conn=73358 op=2 RESULT tag=97 err=53 text=unauthenticated bind (DN with no password) disallowed



In Ingo it was a line in Storage.php (see http://bugs.horde.org/ticket/7418), but that&#039;s not the case here I don&#039;t think. </description> 
   <pubDate>Wed, 06 May 2009 11:08:38 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54021</link> 
  </item> 
   
  <item> 
   <title>There are five places in kronolith where the preference syst</title> 
   <description>There are five places in kronolith where the preference system is being instanciated:

I see only the need to patch one place (see attachment).

Please correct me if i&#039;m wrong.



grep -n &quot;Prefs::&quot; * -r



&gt; kronolith/fb.php:36:        $prefs = &amp;Prefs::singleton($conf[&#039;prefs&#039;][&#039;driver&#039;], &#039;kronolith&#039;, $user, &#039;&#039;, null, false);

the logged-in users password won&#039;t help here, because fb.php is accessed by some other user? so there is no need for a patch.



&gt;kronolith/lib/Kronolith.php:1796:        $prefs = &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

needs to be patched. see attachment



&gt;kronolith/lib/api.php:1348:                    $prefs = &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

the alarms of the logged in users should be retrieved via $prefs = &amp;$GLOBALS[&#039;prefs&#039;]; for other users, the logged-in user password won&#039;t help, i think. no

patch needed



&gt;kronolith/scripts/agenda.php:75:        $prefs = Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

Script, no need for user password.



&gt;kronolith/scripts/upgrades/convert_to_utc.php:52:        $prefs = Prefs::factory($conf[&#039;prefs&#039;][&#039;driver&#039;], &#039;horde&#039;,

Script, no need for user password.</description> 
   <pubDate>Thu, 07 May 2009 12:27:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54033</link> 
  </item> 
   
  <item> 
   <title>&gt; There are five places in kronolith where the preference sy</title> 
   <description>&gt; There are five places in kronolith where the preference system is 

&gt; being instanciated:

&gt; I see only the need to patch one place (see attachment).

&gt; Please correct me if i&#039;m wrong.

&gt;

&gt; grep -n &quot;Prefs::&quot; * -r

&gt;

&gt;&gt; kronolith/fb.php:36:        $prefs = 

&gt;&gt; &amp;Prefs::singleton($conf[&#039;prefs&#039;][&#039;driver&#039;], &#039;kronolith&#039;, $user, &#039;&#039;, 

&gt;&gt; null, false);

&gt; the logged-in users password won&#039;t help here, because fb.php is 

&gt; accessed by some other user? so there is no need for a patch.

&gt;

&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs = 

&gt;&gt; &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt; needs to be patched. see attachment

&gt;

&gt;&gt; kronolith/lib/api.php:1348:                    $prefs = 

&gt;&gt; &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt; the alarms of the logged in users should be retrieved via $prefs = 

&gt; &amp;$GLOBALS[&#039;prefs&#039;]; for other users, the logged-in user password 

&gt; won&#039;t help, i think. no

&gt; patch needed

&gt;

&gt;&gt; kronolith/scripts/agenda.php:75:        $prefs = 

&gt;&gt; Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt; Script, no need for user password.

&gt;

&gt;&gt; kronolith/scripts/upgrades/convert_to_utc.php:52:        $prefs = 

&gt;&gt; Prefs::factory($conf[&#039;prefs&#039;][&#039;driver&#039;], &#039;horde&#039;,

&gt; Script, no need for user password.



Thanks - this fixes the error for me. I grepped for getUser which was the string used in the Ingo issue, should have grepped for Prefs:: as you mentioned. </description> 
   <pubDate>Thu, 07 May 2009 21:56:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54047</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs = 

&gt;&gt; &amp;P</title> 
   <description>&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs = 

&gt;&gt; &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt; needs to be patched. see attachment



This is actually the same like in all the other cases, $user might be the current user, but not necessarily. Thus the password should only be used if $user is the current user.</description> 
   <pubDate>Tue, 12 May 2009 14:07:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54082</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs =

&gt;&gt;&gt; &amp;</title> 
   <description>&gt;&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs =

&gt;&gt;&gt; &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt;&gt; needs to be patched. see attachment

&gt;

&gt; This is actually the same like in all the other cases, $user might be 

&gt; the current user, but not necessarily. Thus the password should only 

&gt; be used if $user is the current user.



Jan - without the patch I get an error on Kronolith&#039;s first save of a new event after logon. With the patch I don&#039;t get the error. So it&#039;s working for me. 



From what you are saying though I understand that there are times that Kronolith uses this code to call users other than the current user at times?



In which case does the code need to be split to obtain the password for when it&#039;s current user as per the patch that fixes my error message?</description> 
   <pubDate>Tue, 12 May 2009 23:31:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54105</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs =

&gt;&gt;&gt; &amp;</title> 
   <description>&gt;&gt;&gt; kronolith/lib/Kronolith.php:1796:        $prefs =

&gt;&gt;&gt; &amp;Prefs::singleton($GLOBALS[&#039;conf&#039;][&#039;prefs&#039;][&#039;driver&#039;],

&gt;&gt; needs to be patched. see attachment

&gt;

&gt; This is actually the same like in all the other cases, $user might be 

&gt; the current user, but not necessarily. Thus the password should only 

&gt; be used if $user is the current user.

Ok, thanks.

The updated patch should now do exactly the above.</description> 
   <pubDate>Fri, 15 May 2009 15:46:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54187</link> 
  </item> 
   
  <item> 
   <title>Closed in favor of the catch-all ticket #8353.</title> 
   <description>Closed in favor of the catch-all ticket #8353.</description> 
   <pubDate>Tue, 16 Jun 2009 13:37:51 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8246#t54605</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
