[
https://issues.apache.org/jira/browse/DIRSERVER-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600728#action_12600728
]
Emmanuel Lecharny commented on DIRSERVER-1181:
----------------------------------------------
So it seems that ldapsearch is also faulty.
My interpretation is that JNDI none ldapsearch implement correctly the
substring filter. Looking at the ASN.1 grammar, you get :
SubstringFilter ::= SEQUENCE {
type AttributeDescription,
-- initial and final can occur at most once
substrings SEQUENCE SIZE (1..MAX) OF substring CHOICE {
initial [0] AssertionValue,
any [1] AssertionValue,
final [2] AssertionValue } }
In this case, each sub element in the filter must be a 'any' element. For
instance, *x*y*z* should translate to :
initial : '*'
any[0] : 'x'
any[1] : 'y'
any[2] : 'z'
final : '*'
This is not what we have.
Question now is : do we have to consider that if 'any' contains x*y*z we have
to split it into 3 parts ?
Another thing is to test that using \2A does not break the search (as \2A means
the substring search for entry where the attribute contains a '*', like in
'cn=a * is born'
> Too many results when using searchfilter with escaped asterisks \2A
> -------------------------------------------------------------------
>
> Key: DIRSERVER-1181
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1181
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.3, 1.5.2
> Reporter: Stefan Seelmann
> Assignee: Emmanuel Lecharny
> Attachments: DIRSERVER_1181_Test.java
>
>
> A search request with such a search filter
> (cn=*x\*y\*z\*) or (cn=*x\2Ay\2Az\2A)
> returns all the entries containing an "cn" attribute
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
