| Emmanuel Lecharny (JIRA) 2006-08-28, 1:12 pm |
| [ http://issues.apache.org/jira/brows...ER-309?page=all ]
Emmanuel Lecharny resolved DIRSERVER-309.
-----------------------------------------
Resolution: Duplicate
This is DIRSERVER-711. No need to have two JIRAs for the same issue !
> 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
> Issue Type: Bug
> Components: ldap
> Reporter: Alex Karasulu
> Assigned To: 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 PD
U 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/j...-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. The
n 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/secur...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|