[jira] Resolved: (DIRSERVER-768) privide debug output in org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()

["Emmanuel Lecharny (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRSERVER-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-768.
-----------------------------------------

    Resolution: Fixed

Some log has been added so that the Principal and the Operation are dumped if some unauthenticated user tries to do something not allowed.

The Credentials is never kept in memory for security reasons, so it's always discared and can't be dumped.

Fixed in 
http://svn.apache.org/viewvc?rev=655571&view=rev
http://svn.apache.org/viewvc?rev=655572&view=rev

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