Access Denied using Impersonation

[Ryan]

I am developing an intranet application that uses windows
authentication and impersonation. The problem I'm having
is that it seems when the session ends the access token
is lost (just a guess) and when the user tries to load
the page again an Access Denied error is generated. Has
anyone experienced this before and know of a workaround.

Any help is greatly appreciated. Thank You!

Ryan

[Holly Mazerolle]

If this is a situation where the user is logged on to a domain and you are
using Windows Integrated Authentication in IIS the session should not
matter. Even if the session ends, on the next request, the same credentials
should be passed to the server and used. If you think it is the session, a
good test would be to lower the timeout to maybe 5 mins and try the same
steps with that.

You can find the timeout setting in the web.config file. Another thing you
could do if you are not sure what user is really trying to access the file
at the time the error occurs would be to run filemon from
[url]www.sysinternals.com[/url]. You can look for Access Denieds and it will also list
the account that is doing the access.

This posting is provided "AS IS" with no warranties, and confers no rights.
Hope this helps.
Holly

[Ryan]

I ran Filemon on the server and found that the domain
user did not have rights for the Inetpub folder. Very
wierd because the user has rights to the web app under
Inetpub and can run the application most of the time.
Just occasionally the user would get an access denied
error. Anyways, I added the domain user to have
read/write priveleges to the Inetpub folder and it seems
to be working. Thank you for you help. By the way, my
wife's name is Holly also, what a coincedence.

Thanks,
Ryan

>-----Original Message-----
>If this is a situation where the user is logged on to a

domain and you are

>using Windows Integrated Authentication in IIS the

session should not

>matter. Even if the session ends, on the next request,

the same credentials

>should be passed to the server and used. If you think it

is the session, a

>good test would be to lower the timeout to maybe 5 mins

and try the same

>steps with that.
>
>You can find the timeout setting in the web.config file.

Another thing you

>could do if you are not sure what user is really trying

to access the file

>at the time the error occurs would be to run filemon

from

>[url]www.sysinternals.com[/url]. You can look for Access Denieds

and it will also list

>the account that is doing the access.
>
>This posting is provided "AS IS" with no warranties, and

confers no rights.

>Hope this helps.
>Holly
>
>.
>

[Holly Mazerolle]

No problem. :-)

Holly