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)" <ji...@apache.org> on 2007/01/25 17:01:49 UTC
[jira] Updated: (DIRSERVER-768) privide debug output in
org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()
[ https://issues.apache.org/jira/browse/DIRSERVER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-768:
----------------------------------------
Fix Version/s: 1.5.0
Sounds a good idea. However, it has been pusched to 1.5 ersion
> privide debug output in org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()
> ---------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-768
> URL: https://issues.apache.org/jira/browse/DIRSERVER-768
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: all
> Reporter: Ralf Hauser
> Fix For: 1.5.0
>
>
> it would be very useful to know whether
> - a principal was found at all
> - if so, which one and
> - whether it contained SECURITY_CREDENTIALS
> This debug output furthermore could provide some more hint (url to a man page/readme) where to find more about the error codes such as
> - "Loop detected (54)"
> - or
> ldap_bind: Internal (implementation specific) error (80)
> additional info: Bind failed: Unexpected exception.
> see also DIRSERVER-763
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.