You'd have to implement this as a Session listener inside Tomcat rather than Turbine to keep some kind of collection of registered usernames and sessions.
You'd then have to build your own tool to query that collection. You could always use the getPerm() of TurbineUser to check for a logged in key (possibly easier). Cameron -----Original Message----- From: Mark Lybarger [mailto:[EMAIL PROTECTED] Sent: 18 May 2004 15:52 To: Turbine Users List Subject: RE: auto logging user out I'm interested to see if the user is logged in via _any_ sessions, not just the current one. We're currently logging users in and using that to restrict access to the application. What i'm after is a way to see if the user is logged in _anywhere_, such as: if ( TurbineSessionTool.isUserLoggedIn( user ) ); // send user to error page w/ message about being able to only log in from one console at a time. > -----Original Message----- > From: Gray, Cameron C. [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 18, 2004 10:21 AM > To: Turbine Users List > Subject: RE: auto logging user out > > > To check for logins maybe $data.getUser.isUserLoggedIn might help.... > > -----Original Message----- > From: Mark Lybarger [mailto:[EMAIL PROTECTED] > Sent: 18 May 2004 15:16 > To: Turbine Users List > Subject: RE: auto logging user out > > I believe we're just running some java script on window close to call > a turbine action to log the user out. I'm not certain, but i'll > check. > > Regarding the single login restriction. I've noticed the SessionTool > in turbine 2.3. Is this a tool that can help us avoid the database > (isUserLoggedIn) flag? It seems to be able to tell if a user is > already logged in by checking all the HttpSession objects for a > particular user? > > thanks! > > > -----Original Message----- > > From: Akmal Sarhan [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, May 18, 2004 2:44 AM > > To: Turbine Users List > > Subject: Re: auto logging user out > > > > > > I am interested to know how did you implement logging the user out > > when they kill the browser. > > > > Am Mo, den 17.05.2004 schrieb Mark Lybarger um 17:09: > > > we have a requirement that a user can only be logged in > > from one session at a time. also we're logging them out when they > > close their browser. we're using a database flag to show > it they're > > logged in, and prevent subsequent logins based on that. > > > > > > the problem is that if the user's session times out when > > logged in (database has isLoggedIn set to true), they won't > be able to > > > re log into our application. is there a way in the turbine > framework > > to tie into the session invalidation? > > i see a setting for the timeout period in the tr.props file, but no > > way to apply a piece of code to run when this happens. > > > > > > any suggestions/insights would be most appreciaited. > > > > > > thanks! > > > mark > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > !EXCUBATOR:40a8d55e296782094351919! > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
