[
https://issues.apache.org/jira/browse/SHIRO-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Les Hazlewood resolved SHIRO-143.
---------------------------------
Assignee: Les Hazlewood
Fix Version/s: 1.0.0
Resolution: Fixed
Hi Paul,
I moved a few other statements to trace and then moved that particular log
statement to the DEBUG level.
A Realm throwing an exception is a normal condition and can happen enough that
a WARN statement could flood the logs. So there are two things you can do now
with the resolution of this issue:
1) Enable the debug level for that class alone and you should see what you
want, or
2) It is ultimately the AuthenticationStrategy implementation to determine (in
the afterAttempt implementation) if this is important enough to be logged, or
the exception rethrown, etc - you could always subclass one of the existing
strategies, and provide a log statement of your choosing if an exception
occurs.
HTH,
Les
> Change logging level from trace to warning in ModularRealmAuthenticator when
> a Realm throws an Exception
> --------------------------------------------------------------------------------------------------------
>
> Key: SHIRO-143
> URL: https://issues.apache.org/jira/browse/SHIRO-143
> Project: Shiro
> Issue Type: Wish
> Components: Realms
> Reporter: Paul Merlin
> Assignee: Les Hazlewood
> Fix For: 1.0.0
>
>
> In ModularRealmAuthenticator.doMultiRealmAuthentication(...) when a Realm
> throws an Exception in getAuthenticationToken(...) it is logged with TRACE
> level.
> At the time of this issue creation (svn rev. 916946), it's at line 257.
> I wish this to be changed to WARNING level for convenience purpose when
> writing a custom Realm and because I feel that's more appropriate.
> WDYT ?
> /Paul
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
