You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2005/12/07 04:14:08 UTC

[jira] Commented: (DIREVE-314) Stack trace overflow when trying to connect with a bad DN

    [ http://issues.apache.org/jira/browse/DIREVE-314?page=comments#action_12359527 ] 

Emmanuel Lecharny commented on DIREVE-314:
------------------------------------------

The problem arise when the server tries to create the matchedName that will be returned in the error message. Yhis is due to the fact that the matchedName method will do a authenticate(), and as the bad DN is the principal, this authenticate() will generate an error, so a matchedName will be created, and this is of course an infinite loop ;=)

Note : I just try to do a Bind with a non existing uid. Fortunatly, we get a StackOverflowException, but the server is still alive !

> Stack trace overflow when trying to connect with a bad DN
> ---------------------------------------------------------
>
>          Key: DIREVE-314
>          URL: http://issues.apache.org/jira/browse/DIREVE-314
>      Project: Directory Server
>         Type: Bug
>     Reporter: Emmanuel Lecharny
>     Assignee: Alex Karasulu
>     Priority: Critical
>  Attachments: stackTrace.log
>
> When trying to Bind with a bad DN, I get a StackTraceOverflow exception.
> I use uid=adminBad, for instance

-- 
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