[
https://issues.apache.org/jira/browse/SHIRO-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Stamer updated SHIRO-391:
-----------------------------
Description:
Sometimes it is useful to log the user name. That way it can easily be traced
which user faced an exception or where an error occurred.
The Mapped Diagnostic Context (MDC) of SLF4J can be used for that as it uses
the same mechanisms as Shiro already does. That way one can use
%X{shiroSubject} in the log pattern. This will then be filled with the
principal name or left blank.
Remark: No additional libraries or anything are necessary for that. All that's
needed is SLF4J and that's there already.
was:
Sometimes it is useful to log the user name. That way it can easily be traced
which user faced an exception or where an error occurred.
The Mapped Diagnostic Context (MDC) of SLF4J can be used for that as it uses
the same mechanisms as Shiro already does. That way one can use %{shiroSubject}
in the log pattern. This will then be filled with the principal name or left
blank.
Remark: No additional libraries or anything are necessary for that. All that's
needed is SLF4J and that's there already.
> Enable Principal in Logs using SLF4J MDC
> ----------------------------------------
>
> Key: SHIRO-391
> URL: https://issues.apache.org/jira/browse/SHIRO-391
> Project: Shiro
> Issue Type: Improvement
> Reporter: Jan Stamer
> Assignee: Jared Bunting
> Priority: Minor
> Attachments: ThreadContext.java.patch
>
>
> Sometimes it is useful to log the user name. That way it can easily be traced
> which user faced an exception or where an error occurred.
> The Mapped Diagnostic Context (MDC) of SLF4J can be used for that as it uses
> the same mechanisms as Shiro already does. That way one can use
> %X{shiroSubject} in the log pattern. This will then be filled with the
> principal name or left blank.
> Remark: No additional libraries or anything are necessary for that. All
> that's needed is SLF4J and that's there already.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
