OK, I guess this is beyond my newbie brain LOL
I have a workstation (Win2k on Win2k domain) that is used by employees to check their schedules. It sits in a common area and is logged in under a very restricted account I created as sort of a "general" account so everyone could see the ASP page that displays today's schedule.
Also on that page are links to a personal page for each user, which displays their upcoming schedule. These pages have domain security permissions set so that only the employee it's meant for has access. When they click on the link for their name a Windows Network Login box pops up and they have to enter their own login info to gain access to their personal schedule page. Then they are returned to the default "today's schedule" page. This way we can provide users with their own schedule without people whining about "who got what job"...
All of this works just fine. However, once the user has checked his/her schedule, ANYONE can access it after that by just clicking on the link for their name - the network login box is no longer displayed! Obviously their network accout permissions are persisting.
What I want to happen is that they will return to the default page, and only the "general" accout permissions would be in effect. Apparently what I'm getting is permissions in effect for general + user1 + user2 + whoever else checks their schedule.
I was hoping it would be something as simple as "session.abandon", but that doesn't seem to have any effect. Would it make any difference if the personal schedule page opened in a new browser window, so when the window was closed the user's network session was destroyed? Am I looking at a domain setting issue? Or perhaps using "session.abandon" incorrectly? (I put it at the very end of the ASP response page code)
Any thoughts would be appreciated
I have a workstation (Win2k on Win2k domain) that is used by employees to check their schedules. It sits in a common area and is logged in under a very restricted account I created as sort of a "general" account so everyone could see the ASP page that displays today's schedule.
Also on that page are links to a personal page for each user, which displays their upcoming schedule. These pages have domain security permissions set so that only the employee it's meant for has access. When they click on the link for their name a Windows Network Login box pops up and they have to enter their own login info to gain access to their personal schedule page. Then they are returned to the default "today's schedule" page. This way we can provide users with their own schedule without people whining about "who got what job"...
All of this works just fine. However, once the user has checked his/her schedule, ANYONE can access it after that by just clicking on the link for their name - the network login box is no longer displayed! Obviously their network accout permissions are persisting.
What I want to happen is that they will return to the default page, and only the "general" accout permissions would be in effect. Apparently what I'm getting is permissions in effect for general + user1 + user2 + whoever else checks their schedule.
I was hoping it would be something as simple as "session.abandon", but that doesn't seem to have any effect. Would it make any difference if the personal schedule page opened in a new browser window, so when the window was closed the user's network session was destroyed? Am I looking at a domain setting issue? Or perhaps using "session.abandon" incorrectly? (I put it at the very end of the ASP response page code)
Any thoughts would be appreciated