Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 34298 invoked from network); 20 Jul 2007 07:59:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jul 2007 07:59:45 -0000 Received: (qmail 22017 invoked by uid 500); 20 Jul 2007 07:59:12 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 21998 invoked by uid 500); 20 Jul 2007 07:59:12 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 21987 invoked by uid 99); 20 Jul 2007 07:59:12 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 00:59:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [81.169.146.162] (HELO mo-p00-ob.rzone.de) (81.169.146.162) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 00:59:09 -0700 Received: from [127.0.0.1] (p548FF42C.dip.t-dialin.net [84.143.244.44]) by post.webmailer.de (mrclete mo51) (RZmta 9.1) with ESMTP id a00d62j6K3fKIp for ; Fri, 20 Jul 2007 09:58:47 +0200 (MEST) Message-ID: <46A06B60.1020100@labeo.de> Date: Fri, 20 Jul 2007 09:59:28 +0200 From: Stefan Zoerner User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: Is ApacheDS 1.5 case-sensitive and whitespace-sensitive? References: <469FC4E1.5030906@webunity.de> <46A05691.2070806@webunity.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RZG-AUTH: kR2YrGeU3i5GJZNxbYfAbITnBeX/YWiFZ/RSZNN7D9RkvGeI24ePHft7 X-RZG-CLASS-ID: mo00 X-Virus-Checked: Checked by ClamAV on apache.org Emmanuel Lecharny wrote: > Well, I would first suggest that you try to see where those %20 are > generated from (it's not into AD, for sure !). If there is nothing you > can do, as DN are parsed during the ASN.1 decoding, and as the DN you > have will be seen as invalid, you will get an exception. The only > solution I see would be to modify the DN parser, which won't be easy > ... I recommend not to modify ApacheDS in order to get this work, because it is an erroneous behavior of the client. How about changing/fixing the Coremedia adapter ("DisIbmDsUserProvider")? Do you have the source code for that or interfaces you can program against? Greetings from Hamburg, Stefan