Click here to Skip to main content
15,794,593 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
MY website is used to administer customer accounts. If I access CustomerA's account through the website then open a new tab and access CustomerB's account the session holding the customer ID updates to think I'm now working on CustomerB. Then if I click back to CustomerA's tab and start editing that page I am in fact editing the database record for CustomerB. This has happened and caused all sorts of problems so I need to find a fool proof way of stopping it. I don't want to put the customer ID in the URL as this will make it open to abuse.

1 solution

IIS creates it's session based on information from the client (and keep it in cookie for trip-around), when you are browsing the same site from the same browser IIS will combine all those queries under the same session.
If browsing different users of the same site from the same browser is a reality for your application you can not use IIS session for state management.
You may read here -[^]...
IMHO you left with two options only:
1. Make you application stateless...
2. Do your own state management...
I have the same issue you have - where the same person - using the same browser - logs in with different accounts...I do assign a GUID to every login and use it to manage session state for that user only...
Share this answer

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

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900