After a bit of help understanding how I can overcome a problem I have at the moment.
We've got a web app that needs to create files on a remote network machine \\TestServer\TestFolder\ for example.
I was expecting to run into the problem of permissions writing stuff to and sure enough, the application throws back an error saying access denied. I've spent the morning doing some reading but I'm still not sure of the best solution.
I'm aware I could use impersonation and get a domain account created and then run the app as that account, then give this account access to the network shares.
However, we're not allowing anonymous access to this web app; only certain people in the domain are going to have access to it. If I call System.Web.HttpContext.Current.User.Identity, will it see the info of the impersonated account, or will it still see the account of the person who accessed the web app?
Web server is Win2K3 and IIS 6.0
Anyone got any suggestions for me?
We've got a web app that needs to create files on a remote network machine \\TestServer\TestFolder\ for example.
I was expecting to run into the problem of permissions writing stuff to and sure enough, the application throws back an error saying access denied. I've spent the morning doing some reading but I'm still not sure of the best solution.
I'm aware I could use impersonation and get a domain account created and then run the app as that account, then give this account access to the network shares.
However, we're not allowing anonymous access to this web app; only certain people in the domain are going to have access to it. If I call System.Web.HttpContext.Current.User.Identity, will it see the info of the impersonated account, or will it still see the account of the person who accessed the web app?
Web server is Win2K3 and IIS 6.0
Anyone got any suggestions for me?
