<?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>change user password fails without anonymous search allowed</title> 
  <pubDate>Sun, 05 Apr 2026 21:30:12 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/3984</link> 
  <atom:link rel="self" type="application/rss+xml" title="change user password fails without anonymous search allowed" href="https://bugs.horde.org/ticket/3984/rss" /> 
  <description>change user password fails without anonymous search allowed</description> 
 
   
   
  <item> 
   <title>Hi,



i&#039;m using the ldap and smbldap backend to let the use</title> 
   <description>Hi,



i&#039;m using the ldap and smbldap backend to let the user change its ldap password.

My ldap server does not allow the anonymous user search the entire user database and I don&#039;t want to provide and admindn for security reasons.



Even with the _passwd_userdn hook enabled, this won&#039;t work as the ldap backend does not respect this hook when connecting for checking for the users existence.



So I wrote a patch that moves the _lookupDN function from smbldap.php to ldap.php and fixes ldap.php to use the same initialisation as smbldap.php using _lookupDN .</description> 
   <pubDate>Tue, 30 May 2006 19:01:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t20770</link> 
  </item> 
   
  <item> 
   <title>The lookupDN method contains a bug using is_null instead of </title> 
   <description>The lookupDN method contains a bug using is_null instead of empty for checking wether admindn is set. This patch includes the last one enhanced by fixing this.</description> 
   <pubDate>Tue, 30 May 2006 19:22:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t20771</link> 
  </item> 
   
  <item> 
   <title>I asked my self why do I need to provide a _passwd_userdn - </title> 
   <description>I asked my self why do I need to provide a _passwd_userdn - Hook if I does not need to provide a similar authentification hook?



The solution are the binddn / bindpw parameters of the ldap authentification plugin.

This means that the backend first connects as the binddn user instead of the anonymous user  to figure out the full userdn and then connects as the user.

This is only a little change to the _lookupDN method.



The patch attached here contains the last patch enhanced by the binddn feature.</description> 
   <pubDate>Tue, 30 May 2006 19:44:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t20773</link> 
  </item> 
   
  <item> 
   <title>see Bug [#3782]</title> 
   <description>see Bug [#3782]</description> 
   <pubDate>Wed, 31 May 2006 20:50:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t20805</link> 
  </item> 
   
  <item> 
   <title>Giving to Jan to pick between the two options.</title> 
   <description>Giving to Jan to pick between the two options.</description> 
   <pubDate>Thu, 01 Jun 2006 03:45:42 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t20813</link> 
  </item> 
   
  <item> 
   <title>Fix committed.</title> 
   <description>Fix committed.</description> 
   <pubDate>Thu, 13 Mar 2008 04:31:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3984#t43789</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
