Hi,

I got a very strange issue with ASP.NET 2.0 asynchronized page call. I
am not user I understand the async. Page call correctly, so I send an
email to this group and hope someone can correct me.

First, I have a web service running on ASP.NET 2.0. In IIS, it is set
to allow windows authentication only. And is running using Network
Service account.
Second, I have a web page which is also running on ASP.NET 2.0. And
also allow windows authentication only. In the web.conf file, I set
authentication mode =  windows, and identity use impersonation. In the
page on_load event, I need to do a async call the the web service to
get some data.

My problem is that, the first time (after IIS reset) the web
application started, the web page uses Network Service account to
access my web service. But all subsequent call, no matter new session
or the old, uses my windows identity to access the web service, which
is expected. Why the web page would use Network Service account to
access the web service the very first time, and change to windows
identity afterward? Is it a by design behavior? How can I make sure my
web page always use windows identity to access the web service, no
matter the web application is restarted or not?

Note, I did not see this happening if I am not using async. Page call.


Thanks,
David

Reply via email to