all groups > iis security > january 2008 >
You're in the

iis security

group:

Problems with writing to a file on IIS 6.0


Problems with writing to a file on IIS 6.0 sarika.koganti@gmail.com
1/24/2008 2:52:31 AM
iis security:
I have an ASP.Net application which accesses a web server hosted on
IIS. The web server creates a file in the application directory and
writes to it. My application needs to run on 2K, 2K3 and XP, i.e. IIS
5.0, 5.1 and 6.0.
I cannot use 'Inegrated Windows Authentication' (on my client's
request) so i have enabled the anonymous access. In 2K and XP systems,
I gave the ASPNET user full control on the physical directory and made
it the id for 'Anonymous Access' for that virtual directory. The
application runs fine.

But on a machine with IIS 6.0, I am facing problems. The user NETWORK
SERVICE has full control on the physical directory, but what should be
the anonymous access user? The NETWORK SERVICE is not available for
anonymous access. Using the IUSR_ id for anonymous access did not help
since it does not have the required permissions. How can I write to
file on IIS 6.0?

Please let me know if there is any way of solving this preferably
without creating a new user account.

Re: Problems with writing to a file on IIS 6.0 sarika.koganti@gmail.com
1/24/2008 11:30:01 PM
The impersonation is set to true in the config file, what would
ASP.NET run as in my case?
And i also need to use the anonymous access to provide access without
any authentication.


[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 Ken Schaefer
1/25/2008 1:55:17 PM
If you are using an ASP.NET application without impersonation, then your
ASP.NET code runs as Network Service (not the anonymous user account in
IIS). There should be no need to make the Network Service account the
anonymous user account.

Cheers
Ken

[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 sarika.koganti@gmail.com
1/27/2008 9:52:46 PM
Do you mean disable the anonymous access and use the integrated
windows authentication instead?
This method works fine, but only when the user logged on is a domain
user account. If the user logs in as the local system admin, the
application fails.


[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 Ken Schaefer
1/27/2008 11:25:20 PM
In that case, the configured IIS anonymous user is used.

By why don't you just disable impersonation? Then IUSR_<machinename> is not
used - instead Network Service is used.

Cheers
Ken

[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 sarika.koganti@gmail.com
1/29/2008 12:11:45 AM
I disabled the impersonation, then I got the 'not authorized to view
this page' error. I had to check the integrated windows authentication
for the application to start.

Is there any disadvantage of using the windows authentication over
anonymous access?

[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 Ken Schaefer
1/29/2008 1:01:08 PM
No,

I am saying disable Impersonation in your web.config, and then ASP.NET pages
will use Network Service (or whatever your web app pool identity is)

Cheers
Ken

[quoted text, click to view]
Re: Problems with writing to a file on IIS 6.0 Ken Schaefer
1/30/2008 12:55:10 PM

[quoted text, click to view]

Then you need to give Network Service access to the pages/resources in
question.

[quoted text, click to view]

No - that should make no difference. Do not set an authentication mode in
web.config, and do not enable impersonation.

[quoted text, click to view]

They are completely different. Windows Authentication means that the end
user must supply Windows credentials to *authenticate*. Anonymous access
means that a preconfigured user account is used.

Impersonation is something completely different to authentication.

Cheers
Ken


[quoted text, click to view]
AddThis Social Bookmark Button