[ http://issues.apache.org/jira/browse/DIRSERVER-660?page=all ]
Emmanuel Lecharny resolved DIRSERVER-660:
-----------------------------------------
Resolution: Fixed
It's funny, because I committed the fix yesturday night, in the next RC4
release. (if you want to test it, just check out this branch :
svn co
http://svn.apache.org/repos/asf/directory/branches/apacheds/optimization-trunks
The log you have is not controlled by a log4j configuration file. It should be
fixed in a way. I will keep the DIRSERVER-486 open until we find a good
solution to this problem.
> Only log passwords on debug level, but not INFO
> -----------------------------------------------
>
> Key: DIRSERVER-660
> URL: http://issues.apache.org/jira/browse/DIRSERVER-660
> Project: Directory ApacheDS
> Type: Bug
> Components: ldap
> Environment: windows, linux
> Reporter: Ralf Hauser
>
> So far, I have not configured apacheDS logging and I always see
> 33768450 [IoThreadPool-1] INFO
> org.apache.directory.server.ldap.LdapProtocolProvider$LdapProtocolHandler -
> [/127.0.0.1:34100] RECEIVED: BindRequest
> Version : '3'
> Name : '[EMAIL PROTECTED]'
> Simple authentication : '111111/0x31 0x31 0x31 0x31 0x31 0x31 '
> While in a development environment, it is ok to log this, in a production
> environment it is not. I guess quite some production environments use the
> default, i.e. INFO
> furthermore, http://www.slf4j.org/docs.html is not particularly helpful how
> to change this...
--
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
