<?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 objectclass lookups fail due to case sensitivity on objectclass match</title> 
  <pubDate>Fri, 10 Apr 2026 12:41:19 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7694</link> 
  <atom:link rel="self" type="application/rss+xml" title="LDAP objectclass lookups fail due to case sensitivity on objectclass match" href="https://bugs.horde.org/ticket/7694/rss" /> 
  <description>LDAP objectclass lookups fail due to case sensitivity on objectclass match</description> 
 
   
   
  <item> 
   <title>Hi there,



I&#039;ve just upgraded one of our customer installa</title> 
   <description>Hi there,



I&#039;ve just upgraded one of our customer installations from HGWE 1.1 to 1.2, and have come across a bug releated to case-sensitivity which prevents users from even logging onto the new 1.2 edition.



What happens is that  _getObjectClasses() returns an associative array of the objectclasses related to a particular DN, and the LDAP server in question contains the specified objectclass but in lower-case rather than camel-case format. This means that the ldapsearch output looks something like this:





dn: uid=foo,dc=some,dc=domain

...

objectClass: kolabinetorgperson

...



# search result

search: 2

result: 0 Success



# numResponses: 2

# numEntries: 1





The problem is related to this piece of code in lib/Horde/Kolab/Server/ldap.php within the _determineType() method:



if (!in_array(&#039;kolabInetOrgPerson&#039;, $oc)) {

...

}



It should be reasonably obvious that the reason the login fails is because the associative array stores the value returned from LDAP in lower case, while the current code is looking for the camel-case version. Temporarily changing the code so that it matches on &#039;kolabinetorgperson&#039;, all in lower-case, allows the login to proceed correctly.



AFAICT objectclasses are by RFC definition aaply case-insensitive matching, so it may be that the simplest fix is to force all objectclasses for a given DN to lower case before putting them in the associative array, and then performing all comparisons in the code with lower case names. However, I am not sure whether or not this will have any further unexpected side-effects.





ATB,



Mark.

</description> 
   <pubDate>Mon, 17 Nov 2008 13:51:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t50798</link> 
  </item> 
   
  <item> 
   <title>ping?</title> 
   <description>ping?</description> 
   <pubDate>Wed, 26 Nov 2008 14:55:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t50956</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/framework/Kolab_Server/lib/Horde/Kolab/Server/ldap.php?rt=horde&amp;r1=1.6&amp;r2=1.7&amp;ty=u
http://cvs.horde.org/diff.php/framework/Kolab_Server/package.xml?rt=horde&amp;r1=1.19&amp;r2=1.20&amp;ty=u
http://cvs.horde.org/diff.php/framework/Kolab_Server/test/Horde/Kolab/Server/ldapTest.php?rt=horde&amp;r1=1.5&amp;r2=1.6&amp;ty=u
http://cvs.horde.org/diff.php/framework/Kolab_Server/test/Horde/Kolab/Server/testTest.php?rt=horde&amp;r1=1.10&amp;r2=1.11&amp;ty=u</description> 
   <pubDate>Mon, 29 Dec 2008 06:48:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t51468</link> 
  </item> 
   
  <item> 
   <title>Fixed in cvs.</title> 
   <description>Fixed in cvs.</description> 
   <pubDate>Mon, 29 Dec 2008 07:01:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t51469</link> 
  </item> 
   
  <item> 
   <title>&gt; Fixed in cvs.



Thank you so much for doing this - it was</title> 
   <description>&gt; Fixed in cvs.



Thank you so much for doing this - it was going to be one of my first jobs this year! One question: I&#039;ve had a look at the nightly builds, and can&#039;t figure out how to download the nightly equivalent snapshot of horde webmail edition for testing :(  Any pointer as to how I can recreate the tarball based upon the code in CVS?





Many thanks,



Mark.

</description> 
   <pubDate>Mon, 05 Jan 2009 10:00:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t51547</link> 
  </item> 
   
  <item> 
   <title>The full webmail package will be hard to recreate from CVS. </title> 
   <description>The full webmail package will be hard to recreate from CVS. Jan always has to put a lot of effort into a release. I&#039;d rely on a single patch then. Do you use the Kolab patch for Horde webmail? Adding another patch should not be too hard.</description> 
   <pubDate>Thu, 08 Jan 2009 21:36:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7694#t51623</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
