Re: How to: A user logs in from a second location and the first location's session gets killed?

2009-10-29 Thread j0n4s.h4rtm...@googlemail.com
Which token? Where do I get that ID from? The whole Session? On Oct 28, 7:12 pm, Miles J mileswjohn...@gmail.com wrote: You need to save the session ID/token to the database. On each page load you check to see if the current ID/token matches the one in the database, if it does not, you log

How to: A user logs in from a second location and the first location's session gets killed?

2009-10-28 Thread j0n4s.h4rtm...@googlemail.com
Hi, the subject essentially asks the whole question already. How did you detect that a user logs in from a second location, and kick him from the first location? The first location should display a warning on the next action that requires to be logged in like You have been logged out

Re: How to: A user logs in from a second location and the first location's session gets killed?

2009-10-28 Thread Miles J
You need to save the session ID/token to the database. On each page load you check to see if the current ID/token matches the one in the database, if it does not, you log them out. So if A logs in and has a token, hell be fine. Once B logs in, a new token is created nad logged in the database. A