You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Ralf Hauser (JIRA)" <ji...@apache.org> on 2006/07/02 09:17:30 UTC

[jira] Commented: (DIRMINA-114) All session log messages should be logged via SessionLog

    [ http://issues.apache.org/jira/browse/DIRMINA-114?page=comments#action_12418825 ] 

Ralf Hauser commented on DIRMINA-114:
-------------------------------------

see DIRSERVER-660 for security issues with this approach - there should be a way to adapt the log level depending on the message content/type received or at least mask out sensitive information such as 

   Simple authentication : '1****** ' 

> All session log messages should be logged via SessionLog
> --------------------------------------------------------
>
>          Key: DIRMINA-114
>          URL: http://issues.apache.org/jira/browse/DIRMINA-114
>      Project: Directory MINA
>         Type: Improvement

>     Versions: 0.8
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>     Priority: Minor
>      Fix For: 0.9

>
> Some users don't want to use another logging framework (or facade) like SLF4J.  At least we could make it easy for them to modify MINA to get rid of SLF4J dependency.  To do so, all session log messages should be forwarded to org.apache.mina.util.SessionLog so that they can simply override that class.
> Additionally the users will have to replace DefaultExceptionMonitor which logs messages which is not for a specific session.

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