------=_Part_125517_21113365.1176969864256
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
After further debugging i found the following behaviour:
The entry has the uid attribute correctly initialized: uid
S287384.
If the uid starts with a capital letter then using these two
filters:
(uid=S287384) or (uid=s287384) doesn't return any result.
If the uid attribute starts with a lower case letter ( i.e.
uid=s287384 )
then both filters work and return the entry.
The definition of the uid attribute is embodied in openldap
source code and
from what i have seen it should be treated as a case
insensitive attribute.
How to explain this behaviour??
Best Regards,
Juri.
------=_Part_125517_21113365.1176969864256
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div>After further debugging i found the following
behaviour:</div>
<div> </div>
<div>The entry has the uid attribute correctly
initialized: uid S287384.</div>
<div> </div>
<div>If the uid starts with a capital letter then
using these two filters:</div>
<div> </div>
<div>(uid=S287384) or (uid=s287384) doesn't
return any result.</div>
<div> </div>
<div>If the uid attribute starts with a lower case
letter ( i.e. uid=s287384 ) then both filters work and
return the entry.</div>
<div>The definition of the uid attribute is embodied
in openldap source code and from what i have seen it should
be treated as a case insensitive attribute. How to explain
this behaviour??</div>
<div> </div>
<div>Best Regards,</div>
<div>Juri.</div>
------=_Part_125517_21113365.1176969864256--
|
