In 2.x, we've removed the userCache because the Acegi folks recommend using the persistent frameworks' cache if it has one.
http://forum.springframework.org/showthread.php?t=19815 You could try removing the cache in your application in your application as well: http://fisheye4.cenqua.com/changelog/appfuse?cs=2559 Matt On 3/15/07, Jarek Gilewski <[EMAIL PROTECTED]> wrote:
mraible wrote: > > The context information may be stored in the user's session, which > would make it hard for you to modify as an administrator. > I would like to refresh SecurityContext every time the User object properties (which is logged in) are changed. Right now the only way to have current and fresh information about loogged in user is: // Get current user information SecurityContext sctx = SecurityContextHolder.getContext(); Authentication auth = sctx.getAuthentication(); User user = (User)auth.getPrincipal(); user = userManager.loadUserByUsername(user.getUsername()); Is there another way? What is the purpose for the userCache.removeUserFromCache(user.getUsername())? What happen when the user is in cache (when the user is put in?) and what if the admin removes another user from cahche (during changing user information where UserSecurityAdvice is called). Regards Jarek -- View this message in context: http://www.nabble.com/UserCache-vs-SecurityContext-tf3400798s2369.html#a9489752 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
