Apache Directory Project - [jira] Commented: (DIREVE-294) Search filters with wrong case in attribute names lead

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > October 2005 > [jira] Commented: (DIREVE-294) Search filters with wrong case in attribute names lead





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Commented: (DIREVE-294) Search filters with wrong case in attribute names lead
Alex Karasulu (JIRA)

2005-10-26, 2:45 am

[ http://issues.apache.org/jira/brows...action_12355914 ]

Alex Karasulu commented on DIREVE-294:
--------------------------------------

I am really sorry about this screw up. It was a bug deep in the BootstrapOidRegistry that caused this. For some reason I think this was the first time we triggered the execution of the code this way. Anyhow its fix and I appologize for any runaround thi
s may have caused you.

> Search filters with wrong case in attribute names lead to wrong result
> ----------------------------------------------------------------------
>
> Key: DIREVE-294
> URL: http://issues.apache.org/jira/browse/DIREVE-294
> Project: Directory Server
> Type: Bug
> Reporter: Stefan Zoerner
> Assignee: Alex Karasulu
> Fix For: 0.9.3


>
> Search filters which use attribute names with "wrong" case cause the search operation to return nothing. Example:
> $ ldapsearch -D "uid=admin,ou=system" -w ***** -p 10389 -b "dc=apache,dc=org" -s base "(Objectclass=*)"
> (nothing)
> $
> But the following still works as expected:
> $ ldapsearch -D "uid=admin,ou=system" -w secret -p 10389 -b "dc=apache,dc=org" -s base "(objectClass=*)"
> dc=apache,dc=org
> dc=apache
> objectClass=extensibleObject
> objectClass=domain
> objectClass=top
> I assume the error is due to changes in class NormalizationService (package org.apache.ldap.server.normalization) done to fix DIREVE-274, because if "wrong" attributes are used, this interceptor raises WARN messages like
> [23:37:27] WARN [org.apache.ldap.server.normalization.NormalizationService] - undefined filter based on undefined attributeType 'Objectclass' not evaluated at all. Returning empty enumeration.
> which explains the behavior above.
> Btw.: The behavior causes Softerra LDAP Administrator 3.2.1 to fail during the exploration of entries. This is how I found it.


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com