shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SHIRO-354) Authentication cache
Date Fri, 15 Jul 2016 14:43:21 GMT

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

Brian Demers closed SHIRO-354.
------------------------------
    Resolution: Fixed

> 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)

Mime
View raw message