DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15322>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15322 UserManagement: multiple runtime instances for the same user ------- Additional Comments From [EMAIL PROTECTED] 2002-12-12 17:58 ------- I believe its not a turbine issue, since we removed all turbine security objects from Jetspeed in 1.4b1. Its appears to be up to the Authentication service to set this. >From TurbineAuthentication.java (or LDAP): // Mark the user as being logged in. user.setHasLoggedIn(new Boolean(true)); The 'bug' is in Jetspeed, and the fact that getUsers() doesn't use the cache. >From TurbineUserManagement.java: users = TurbineUserPeer.doSelectUsers(criteria); Now using a cache to determine if a user is logged on, is also a problem in clustered deployments. In order to get this to work properly, when the user logs on, the user record must be updated on the database. There will also need to be servlet event handlers for shutdown and session expiration. Also, you need to keep a count of logins, since a user can logon to multiple sessions on the same servers or different servers. It is not a trivial problem. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
