Session ID Sharing Issue

Question

0.00/5 (No votes)

See more:

I've recently been developing a website using asp.net webforms that uses in proc sessions and I noticed that session ids are shared amongst browser tabs. So I was wondering what you would do for the following situations:

Problem: Multiple logins with different users in the one browser problem

User opens browser tab 1, logins with "user1" - store in session
User opens browser tab 2, logins with "user2" - store in session
At this stage session information is now pointing to "user2" because of how session id is shared amongst browser tabs
User tries an action on tab 1 and suddenly they have "user2" information
How do you alert the user in tab 1 that the user has changed or how do force tab1 user to logout?

Appreciate anyone letting me know of any alternatives or best practices for the above problem

Posted 28-Nov-13 1:55am

rocky_em

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jobless Creature · Answer 1 · 2013-11-28T05:16:00

One alternative would be using the cookie less session where in the session ID is sent in the URL for individual browser requests. So 2 concurrent users will be allowed to use the application in different tabs.

If you are sure of logging out the user 1 since user 2 has logged in, then one way is that you can maintain a mapping table of users and the asp.net session ID. The moment user 2 logs in, the session ID of user 1 will be replaced with user 2's session ID and a comparison in mapping table will reveal that user 1 must be logged out.

Karthik_Mahalingam · Answer 2 · 2013-11-28T06:03:00

Solution 2

You have to understand that Session values are stored in the server code not in the browser..

so all the tabs will be having the last updated session values...

add a condition that, if session is not null then dont allow to create a new instance of session.

Thanks.
karthik

Posted 28-Nov-13 6:03am

Karthik_Mahalingam

NITDGP2005 · Answer 3 · 2013-11-28T06:19:00

Solution 4

This is very much similar to "Switch Account"

Posted 28-Nov-13 6:19am

NITDGP2005