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

Posted to dev@shiro.apache.org by "Brian Demers (JIRA)" <ji...@apache.org> on 2016/07/15 14:43:20 UTC

[jira] [Reopened] (SHIRO-353) DefaultSecurityManager has invalid SLF4J log instruction

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

Brian Demers reopened SHIRO-353:
--------------------------------

> DefaultSecurityManager has invalid SLF4J log instruction
> --------------------------------------------------------
>
>                 Key: SHIRO-353
>                 URL: https://issues.apache.org/jira/browse/SHIRO-353
>             Project: Shiro
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Maciej Ziarko
>            Priority: Trivial
>             Fix For: 1.2.1
>
>   Original Estimate: 2m
>  Remaining Estimate: 2m
>
> Invalid SLF4J message (string concatenation with {} inside template) in DefaultSecurityManager class.
> Line 550:
> log.debug("Logging out subject with primary principal {}" + principals.getPrimaryPrincipal());
> Should be:
> log.debug("Logging out subject with primary principal {}", principals.getPrimaryPrincipal());



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)