Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 90835 invoked from network); 10 Feb 2006 05:24:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Feb 2006 05:24:06 -0000 Received: (qmail 92645 invoked by uid 500); 10 Feb 2006 05:24:03 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 92562 invoked by uid 500); 10 Feb 2006 05:24:03 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 92531 invoked by uid 99); 10 Feb 2006 05:24:03 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2006 21:24:01 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 08BC6193 for ; Fri, 10 Feb 2006 06:23:08 +0100 (CET) Message-ID: <929235895.1139548988033.JavaMail.jira@ajax.apache.org> Date: Fri, 10 Feb 2006 06:23:08 +0100 (CET) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Updated: (DIRSERVER-309) Decoder does no give sufficient information about errors so the LDAP server can respond with correct result code. In-Reply-To: <1833487465.1138916765508.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DIRSERVER-309?page=all ] Alex Karasulu updated DIRSERVER-309: ------------------------------------ Component: ldap > Decoder does no give sufficient information about errors so the LDAP server can respond with correct result code. > ----------------------------------------------------------------------------------------------------------------- > > Key: DIRSERVER-309 > URL: http://issues.apache.org/jira/browse/DIRSERVER-309 > Project: Directory ApacheDS > Type: Bug > Components: ldap > Reporter: Alex Karasulu > Assignee: Emmanuel Lecharny > > Right now a communication exception is thrown by the server when a malformed DN is given in a PDU. I tested this with bind for example using a bad BindDN. When the ASN1 codec fails the server cannot really tell the difference between a bad protocol PDU which causes a protocolError (2) resulting in a JNDI CommunicationException from a bad DN which should return a resultCode of namingViolation (64) which in JNDI comes back to the client as an InvalidNameException. For more info on resultCodes mapping to JNDI exceptions see: > http://java.sun.com/products/jndi/jndi-ldap-gl.html#EXCEPT > Basically the ASN1 decoder has to throw exceptions with hints regarding the failure to allow the server to respond appropriately to the client. This can be done by embedding additional info such as a result code in an subclass of DecoderException. Then the LdapProtocolProvider can access this info. > This problem is a direct result of trying to parse a DN for correctness when this is not the responsibility of the ASN1 codec. The LDAP BER codec should be giving stuff back to the server as is and letting the server determine whether or not the dn or other (non-asn1 constrained) constructs are invalid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira