Hi all.
I'm designing a system consists of 3 parts:
1.web client app
2. web service router
3. web service
Web client app. calls web service via router. ( I successfully implemented
this kind of behavior using anonymous access.)
Now, when I try to use windows authentication, the web service router is
not calling the dest. web service any more.
I added these two lines in all web.config files
<authentication mode="Windows" />
<identity impersonate="true"/>
but without success.
When I call the dest web service directly (without routing) everything is
O.K.
So, I think that the problem resides on a web service router's side.
I think that I might need to pass credentials in a RouterHandler unit,
but I don't know how to do that.
Any help will be appreciated.
Trebor
Don Yeske - 11 Nov 2004 22:13 GMT
Hope this helps, maybe not:
Bear in mind that Windows 2000 does *NOT* support impersonation by the
ASP.NET worker process account. The reason is that the ASPNET account lacks
the privilege Act As Part of the Operating System. Of course, you wouldn't
want to assign that privilege to ASPNET (which is supposed to be a
limited-privilege account anyway). This is not a problem on later versions
of Windows that use the Network Service account instead of ASPNET. I'm not
sure if it's a problem in XP.
If you need impersonation under 2000, you can change your machine config to
run as another account instead of ASPNET (e.g., LocalSystem), but this is
just as bad as giving ASPNET the requisite privilege.
-- Don
> Hi all.
>
[quoted text clipped - 26 lines]
>
> Trebor