Okay....I've about had my wits end with asp.net web security.........I have a web app that allows a user to export results in .txt fashion to a shared folder residing on the web server. Currently, the folder is shared and has access for "everyone" to write to the folder. When I run the code in debug (localhost) this code does exactly what I want it to do. When I deploy to the server and run it....I get the dreaded:
"ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or Network Service on IIS 6 and IIS 7, and the configured application pool identity on IIS 7.5) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
"
I am running out of ideas and patience to deal with this issue.......currently I've tried
1.) granting "everyone" access to the folder
2.) creating an ASPNET user account and giving it full control
3.) granting Network Service full control to the folder
4.) granting IUSER and II_USER full control to the folder
What am I missing? First and foremost...why is this working just fine in localhost, and failing in production? and what else is out there that I'm missing.....
Frustrated in VA