Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1842874305.1206995545150.JavaMail.jira@brutus>
Date: Mon, 31 Mar 2008 13:32:25 -0700 (PDT)
From: "Alex Karasulu (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Closed: (DIRSERVER-1083) Search on an custom attribute added
 to the dynamic schema fails when no result is found
In-Reply-To: <2053391.1191591770618.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu closed DIRSERVER-1083.
------------------------------------

    Resolution: Invalid

I added a test case here to demonstrate what's going on:

   http://svn.apache.org/viewvc?view=rev&revision=643127

LDAP search requires matchingRule to figure out how to conduct candidate matching for various assertions.  Without a matchingRule on the attributes used in filter assertions, the server cannot effectively search for your entry based on your search criteria.  The server uses comparators and normalizers that are associated matchingRules to normalize and compare values.

Right now the server is defaulting to no op normalizers and comparators when it cannot find a matchingRule for this attribute you want to search.  The no-op defaults presumes some binary data.  However you're using a human readable syntax.  So what's happening is the server is treating your attribute value as binary in some places and bombing out when expecting a string in others.

Right now it's pretty sad that the server let you search on this attribute at all without matchingRules.  I don't know if attributeType definitions without MRs are allowed in LDAP.  I thought they are but if they don't have a matchingRule they cannot be used in the DN or in filter expressions.  I may be wrong.  

Please confirm with the RFCs for the exact behavior under these circumstances and I'll make sure we comply. Thanks!

> Search on an custom attribute added to the dynamic schema fails when no result is found
> ---------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1083
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1083
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: bigbang
>            Reporter: Pierre-Arnaud Marcelot
>            Assignee: Alex Karasulu
>            Priority: Critical
>             Fix For: 1.5.2
>
>         Attachments: active-directory.ldif
>
>
> When searching on a custom attribute added to the dynamic schema, I received an error in Directory Studio:
> Error while performing search
>   [LDAP: error code 80 - failed on search operation: Unexpected exception.]
> This error only occurs when no result is found. If one or more results are found, they are correctly displayed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.