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:21 UTC
[jira] [Updated] (SHIRO-354) Authentication cache
[ https://issues.apache.org/jira/browse/SHIRO-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Demers updated SHIRO-354:
-------------------------------
Fix Version/s: (was: 1.3.0)
> 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
> Labels: authentication, cache
> Fix For: 1.2.1
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)