Simple Machines Community Forum

Customizing SMF => Modifications and Packages => Mod Requests => Topic started by: profile on January 30, 2005, 08:41:44 PM

Title: duplicate login kick/auto logout
Post by: profile on January 30, 2005, 08:41:44 PM
Is there something available to restrict duplicate login similiar to yahoo messenger?  When it's already logged in, either kick both off or the first user off?
Title: Re: duplicate login kick/auto logout
Post by: Pause on February 01, 2005, 05:58:12 AM
Quote from: profile on January 30, 2005, 08:41:44 PM
Is there something available to restrict duplicate login similiar to yahoo messenger?  When it's already logged in, either kick both off or the first user off?
AFAIK, it should already show them as logged in if they go to the page again in another window...
Title: Re: duplicate login kick/auto logout
Post by: profile on February 02, 2005, 04:57:42 PM
Hopefully this will clear it up a little.

Here's an example using smflogin1 as the username:
smfuser1 login at  9am local board time
another person uses smfuser1 to login at 10am local board time

possible end result:
the smfuser1 login at 9am will get kicked off the board -or-
the smfuser1 login at 10am will get a message saying the account is in use
-or- other combination
Title: Re: duplicate login kick/auto logout
Post by: [Unknown] on February 06, 2005, 05:16:43 AM
You're basically asking to have it such that if someone logs into an account, no one else can log into it, yes?

This could be done, but by nature it could cause people login troubles....

-[Unknown]
Title: Re: duplicate login kick/auto logout
Post by: profile on March 17, 2005, 03:19:55 PM
how hard would it be to implement this or where can I go to learn more about something similiar to this?  It would be nice to use this to prevent sharing of accounts, unless there's another way to do it.  yahoo messenger has a similiar function.  TIA
Title: Re: duplicate login kick/auto logout
Post by: [Unknown] on March 17, 2005, 05:29:21 PM
Well, the cleanest way would be to do it based on the session id; make sure there's only one session id logged into one account at a time.  This would mean caching the current session id in the members table, and then checking if that session id exists (if it's in the log_online table.)

-[Unknown]