Re: how to allow only one concurrent login at a time on web

From: Erik Porter [.NET MVP] (erikporter@mvps.org)
Date: 03/30/03 

From: "Erik Porter [.NET MVP]" <erikporter@mvps.org>
Date: Sun, 30 Mar 2003 01:25:13 -0500

You could add an entry to a database with their unique identifier (whatever
that may be in your case, like e-mail, guid, whatever) and the session id.
Then when the session ends, remove that entry from the database. Anytime
someone tries to login, check the database to see if that particular login
already exists.

That being said, I wouldn't recommend trying to do that, because session
timeout by default is 20 minutes, so if that user tried to come back within
20 minutes, they wouldn't be allowed back into the site, because their last
session hadn't timed out yet. You could use a signout button to take care
of this and just end it for them when they hit it, but what if the user
forgot to hit the signout button before leaving?

Hope this gets you thinking :)

Erik Porter
Microsoft .NET MVP
http://www.windowsforms.net

"R. Hariharan" <rajaram_hariharan@yahoo.co.in> wrote in message
news:302401c2f5af$6f424090$3101280a@phx.gbl...
> Hi,
>
> I am working in asp.net. We are currently developing one
> site. Here, at any point of time, unique users should be
> allowed to login in. A user who logged into the site,
> should not be allowed to login in the same userid before
> logged off.
>
> Please give some solutions regarding this.
>
> Thanks.

Quantcast