[
https://issues.apache.org/jira/browse/SHIRO-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421756#comment-13421756
]
Les Hazlewood commented on SHIRO-354:
-------------------------------------
P.S. you can also try out the test your self. If you comment out the last line
of config, you will see the test fail, indicating that caching is working as
expected. Again, if you feel otherwise, please submit a test.
> Authentication cache
> --------------------
>
> Key: SHIRO-354
> URL: https://issues.apache.org/jira/browse/SHIRO-354
> Project: Shiro
> Issue Type: Bug
> Components: Caching
> Affects Versions: 1.2.0
> Environment: irrelevant
> Reporter: Tudor Raneti
> Assignee: Les Hazlewood
> Labels: authentication, cache
> Fix For: 1.2.1, 1.3.0
>
>
> Please see this subject for details:
> http://shiro-user.582556.n2.nabble.com/how-to-log-out-another-user-programatically-authentication-cache-problem-td7420486.html#a7429528
> In short:
> I can't set authenticationCachingEnabled from shiro.ini or realm constructor;
> Even if it were set, as I managed to start an authentication cache, it would
> not work because !isAuthenticationCachingEnabled(token, info) always returns
> true in AuthenticatingRealm.cacheAuthenticationInfoIfPossible, returning w/o
> putting anything on the cache.
> Otherwise the system logs say that it's using the cache...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
