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-379) SimpleAccoutRealm concurrency access to roles and users
Date Fri, 15 Jul 2016 14:48:20 GMT

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

Brian Demers closed SHIRO-379.
------------------------------

> SimpleAccoutRealm concurrency access to roles and users
> -------------------------------------------------------
>
>                 Key: SHIRO-379
>                 URL: https://issues.apache.org/jira/browse/SHIRO-379
>             Project: Shiro
>          Issue Type: Bug
>          Components: Realms 
>    Affects Versions: 1.2.0
>         Environment: Apache Tomcat 6.0.35, Win 7 x64, JDK 1.6.0_32 x64
>            Reporter: Ludovic Garcia
>            Priority: Minor
>             Fix For: 1.2.2
>
>         Attachments: shiro_379.diff
>
>
> I'm using a PropertiesRealm which automatically reload Users and roles if the resource
has been modified.
> And i noticed that authenticating an user and reloading properties file in the same time,
authenticating do not wait for reloading to be finished. 
> Should not SimpleAccountRealm be refactored in order to lock authentication while modifying
users / roles?
> We should simply acquire a Mutex in order to retrieve users / roles or adding / removing
users?
> An other way to ensure concurrency should be to use Collections.synchronizedMap() for
users' map and roles' map, but while reloading resource, authentications won't wait for the
reloading to be finished.
> I can do required changes if it helps 



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

Mime
View raw message