When a user logs into my asp.net 2.0 webapp (user1), I set productID in a session variable:
Session["ProductName"] = value from database
That value gets passed into stored procedures to match with the correct user/product. Anonymous web users can surf over to the webapp like this:
I grab user1 from the URL, look that up in the database and assign Session["ProductName"]. It works the same as above except the anonymous user has only read access. Since Session["ProductName"] already has a value for this anon user, what happens when the user does this in the same browser session but a new window/tab:
Their Session["ProductName"] is ovewritten with user2's info. I want to allow the anon user to view different URLs this way in the same browser without crossing/overwriting sessions. How can I accomodate this for the authenticated logged in user and the anon user?
Thanks.
Session["ProductName"] = value from database
That value gets passed into stored procedures to match with the correct user/product. Anonymous web users can surf over to the webapp like this:
I grab user1 from the URL, look that up in the database and assign Session["ProductName"]. It works the same as above except the anonymous user has only read access. Since Session["ProductName"] already has a value for this anon user, what happens when the user does this in the same browser session but a new window/tab:
Their Session["ProductName"] is ovewritten with user2's info. I want to allow the anon user to view different URLs this way in the same browser without crossing/overwriting sessions. How can I accomodate this for the authenticated logged in user and the anon user?
Thanks.