Disable Concurrent Login In Web Application

I am storing session data in the web browser's cookie and want backend to have active user's information who are currently logged in to the application so that on successful login request I can find out if this particular user already has an active session. If that is possible then I can block the login for that user.

Feb 08, 2016 · Hello, I have a SharePoint web application using Windows Authentication. I got a request from security guys to disable concurrent logins for this web app but because it uses WinAuth I cannot capture the stage at which login is initiated.

Ways to disable concurrent login per user on web application . May Pat. Ranch Hand Posts: 32. posted 17 years ago. Hi folks. I'm assigned to look for ways to prevent a user from concurrently logs in to our web application. I.e. we want a user to log in in one session at a given time.

In order to track user login another way out is handle the Session_Start and Session_End event in Global.asax. You can get the session id when user successfully logged in, just store the session id in your datastore (associate with username). Delete the session id when Session_End event fires or user manually logout.

Feb 09, 2010 · Hi All, we are developing web application with c#.net, our requirment is when user1 is logged into system using userid1, if some other user logs into system with same userid we should expire old session and need to maintain session which is latest loged in. this is applicable for same system or different systems.

We are currently developing a web application. The developers have allowed multiple login. e.g an user can log-in to multiple computers at the same time. They are quoting Gmail account as an example of allowing multiple access. We have secured our web application similar to here.

DZone > Java Zone > Disable multiple logins for same user - Servlets and Sessions. Disable multiple logins for same user - Servlets and Sessions by Waqas Memon ... to login …

If there's too much risk involved, don't do it. If it would convenience the user, consider allowing concurrent logins, perhaps with some caveats, such as only having one active session at a time, or allowing session management to disable sessions, and in …