<?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>Wicked tries (and fails) to bind to LDAP as Page creator</title> 
  <pubDate>Fri, 10 Apr 2026 17:02:52 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8270</link> 
  <atom:link rel="self" type="application/rss+xml" title="Wicked tries (and fails) to bind to LDAP as Page creator" href="https://bugs.horde.org/ticket/8270/rss" /> 
  <description>Wicked tries (and fails) to bind to LDAP as Page creator</description> 
 
   
   
  <item> 
   <title>Setup: Horde 3.3.4-RC1, Wicked 1.0-cvs.



When accessing a </title> 
   <description>Setup: Horde 3.3.4-RC1, Wicked 1.0-cvs.



When accessing a page in Wicked that has been created by another user, Wicked makes a call to LDAP and tries to bind as the page author. The first time after logging on that this occurs results in an error: &quot;The preferences backend is currently unavailable and your preferences have not been loaded. You may continue to use the system with default settings.&quot;



LDAP log:



May 14 00:47:55 server01 slapd[1156]: conn=113175 op=2 BIND dn=&quot;uid=simon,ou=users,dc=simonandkate,dc=lan&quot; method=128 

May 14 00:47:55 server01 slapd[1156]: conn=113175 op=2 RESULT tag=97 err=53 text=unauthenticated bind (DN with no password) disallowed 



On subsequent page accesses the error is still logged by LDAP, but the error message in Horde appears to be suppressed.



This appears to be occurring across several of the Horde apps, see other bug tickets logged over last few weeks - 8269, 8251, 8246, 7418. Jan I notice has commented in a couple of them (in the Kronolith and Nag tickets) as to the user being called not necessarily being the current user. It would appear there is a basic setup issue with the way I (and at least one other) am using LDAP and the Horde code.



I am happy to provide details of my LDAP setup if it will help anyone debugging why Horde is trying to do this.</description> 
   <pubDate>Wed, 13 May 2009 14:53:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54113</link> 
  </item> 
   
  <item> 
   <title>With Horde set to debug logging, logs are as follows for whe</title> 
   <description>With Horde set to debug logging, logs are as follows for when this occurs:



May 15 10:03:00 HORDE [debug] [horde] Connected to the following memcache servers:localhost:11211 [pid 1577 on line 127 of &quot;/usr/share/horde/lib/Horde/Memcache.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Wicked_Driver_sql::_retrieve(): SELECT * FROM wicked_pages WHERE page_name = &#039;Server_Setup&#039; [pid 1577 on line 927 of &quot;/usr/share/horde/wicked/lib/Driver/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Wicked_Driver_sql::logPageView(Server_Setup): UPDATE wicked_pages SET page_hits = page_hits + 1 WHERE page_name = ? [pid 1577 on line 558 of &quot;/usr/share/horde/wicked/lib/Driver/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Wicked_Driver_sql::getPages(): SELECT page_id, page_name FROM wicked_pages [pid 1577 on line 763 of &quot;/usr/share/horde/wicked/lib/Driver/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache miss: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 169 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] SQL Query by DataTree_sql::_exists(): SELECT datatree_id FROM horde_datatree WHERE group_uid = ? AND datatree_name = ? AND datatree_parents = ?, array (

  0 =&gt; &#039;horde.perms&#039;,

  1 =&gt; &#039;wicked&#039;,

  2 =&gt; &#039;&#039;,

) [pid 1577 on line 398 of &quot;/usr/share/horde/lib/Horde/DataTree/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] SQL Query by DataTree_sql::_exists(): SELECT datatree_id FROM horde_datatree WHERE group_uid = ? AND datatree_name = ? AND datatree_parents = ?, array (

  0 =&gt; &#039;horde.perms&#039;,

  1 =&gt; &#039;pages&#039;,

  2 =&gt; &#039;:83&#039;,

) [pid 1577 on line 398 of &quot;/usr/share/horde/lib/Horde/DataTree/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] SQL Query by DataTree_sql::_exists(): SELECT datatree_id FROM horde_datatree WHERE group_uid = ? AND datatree_name = ? AND datatree_parents = ?, array (

  0 =&gt; &#039;horde.perms&#039;,

  1 =&gt; &#039;3&#039;,

  2 =&gt; &#039;:83:84&#039;,

) [pid 1577 on line 398 of &quot;/usr/share/horde/lib/Horde/DataTree/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache set: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 set at 1242345780 expires at 1242432180) [pid 1577 on line 211 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] SQL query by Horde_Alarm_sql::_list(): SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods, alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal FROM horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND alarm_start &lt;= ?) OR alarm_snooze &lt;= ?) AND (alarm_end IS NULL OR alarm_end &gt;= ?) AND (alarm_uid = ? OR alarm_uid = ?) ORDER BY alarm_start, alarm_end [pid 1577 on line 148 of &quot;/usr/share/horde/lib/Horde/Alarm/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Wicked_Driver_sql::_retrieve(): SELECT * FROM wicked_attachments WHERE page_id = 3 [pid 1577 on line 927 of &quot;/usr/share/horde/wicked/lib/Driver/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]

May 15 10:03:00 HORDE [error] [wicked] Error rebinding for prefs writing: [53]: Server is unwilling to perform [pid 1577 on line 270 of &quot;/usr/share/horde/lib/Horde/Prefs/ldap.php&quot;]

May 15 10:03:00 HORDE [error] [wicked] Internal LDAP error.  Details have been logged for the administrator. [pid 1577 on line 348 of &quot;/usr/share/horde/lib/Horde/Prefs/ldap.php&quot;]

May 15 10:03:00 HORDE [error] [wicked] Error rebinding for prefs writing: [53]: Server is unwilling to perform [pid 1577 on line 270 of &quot;/usr/share/horde/lib/Horde/Prefs/ldap.php&quot;]

May 15 10:03:00 HORDE [error] [wicked] Internal LDAP error.  Details have been logged for the administrator. [pid 1577 on line 348 of &quot;/usr/share/horde/lib/Horde/Prefs/ldap.php&quot;]

May 15 10:03:00 HORDE [debug] [wicked] Cache hit: perm_exists_wicked:pages:3 (Id b388c006a6ca2417ee65b88de6435e97 newer than 1242259380) [pid 1577 on line 175 of &quot;/usr/share/horde/lib/Horde/Cache/sql.php&quot;]</description> 
   <pubDate>Fri, 15 May 2009 00:05:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54160</link> 
  </item> 
   
  <item> 
   <title>Can whoever&#039;s been handling these tickets take a look at thi</title> 
   <description>Can whoever&#039;s been handling these tickets take a look at this one too?</description> 
   <pubDate>Thu, 04 Jun 2009 02:24:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54405</link> 
  </item> 
   
  <item> 
   <title>I suspect this is related to configuring LDAP to use per-use</title> 
   <description>I suspect this is related to configuring LDAP to use per-user credentials to bind to LDAP rather than a &quot;system&quot; account that has read and/or write access across the tree.  For most applications this works fine, but there are some places in Horde where it is necessary to access other users&#039; information.  For example: when resolving a user ID into a friendly name, an Identity object is created (backed by Prefs) which is used to try to look up the Personal Information.  If you are using LDAP to store prefs, and LDAP is configured to use the user&#039;s own credentials rather than a single system-type credential, this operation fails.



The question, though, is how to solve it?  In my own environments I have created a Horde user in LDAP that has the appropriate access to all users so it avoids this problem.  But one of the configuration options we allow in Horde currently is to use the user&#039;s own credentials when binding to LDAP.  Do we need to deprecate that feature or make Identity lookup failurs (and other similar cross-user Prefs actions) fail silently since they are &quot;soft&quot; errors?</description> 
   <pubDate>Thu, 04 Jun 2009 13:07:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54420</link> 
  </item> 
   
  <item> 
   <title>Failing silently was what I was looking to do in Ansel when </title> 
   <description>Failing silently was what I was looking to do in Ansel when accessing this information, but currently it&#039;s complicated by the fact that the notification is actually pushed directly from the Prefs_* object where the failure occurs, hence there is no way to differentiate between a identity lookup vs pref lookup as far as silencing errors is concerned.  We would have to remove all of the pushes from the pref code then move notification entirely to client code (where it probably belongs anyway), but that would likely require BC-breaking changes to the pref system so this may be a solution for Horde 4.



It seems to me that per-user binding should probably be deprecated, but I am not an LDAP guy, so I would leave that decision to someone who is more educated then I...</description> 
   <pubDate>Thu, 04 Jun 2009 13:43:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54421</link> 
  </item> 
   
  <item> 
   <title>Please refer my comments at http://bugs.horde.org/ticket/827</title> 
   <description>Please refer my comments at http://bugs.horde.org/ticket/8271#c4



Simon</description> 
   <pubDate>Thu, 04 Jun 2009 23:24:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54429</link> 
  </item> 
   
  <item> 
   <title>Duplicate of bug #8271.</title> 
   <description>Duplicate of bug #8271.</description> 
   <pubDate>Fri, 05 Jun 2009 13:16:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54434</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:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8270#t54606</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
