L
leo_junquera
I am trying to use windows authentication on an intranet to call a web
service. When I make my first call to the service after connecting
from a client app using:
ws.Url = ServiceUrl;
ws.Credentials = System.Net.CredentialCache.DefaultCredentials;
ws.UnsafeAuthenticatedConnectionSharing = true;
It takes forever (2-3 minutes) and my mem usage for aspnet_wp.exe
balloons from 2,952K to 586,264K and stays there.
I am using v1.1.4322 on both client and server. It is set up with
windows authentication using identity impersonate set to true and the
authentication mode of windows in the web.config.
I have wanted to move the architecture towards web services but this is
unusable. Forcing the users to log in would be a step back in their
eyes too.
Any help would be greatly appreciated.
Leo
service. When I make my first call to the service after connecting
from a client app using:
ws.Url = ServiceUrl;
ws.Credentials = System.Net.CredentialCache.DefaultCredentials;
ws.UnsafeAuthenticatedConnectionSharing = true;
It takes forever (2-3 minutes) and my mem usage for aspnet_wp.exe
balloons from 2,952K to 586,264K and stays there.
I am using v1.1.4322 on both client and server. It is set up with
windows authentication using identity impersonate set to true and the
authentication mode of windows in the web.config.
I have wanted to move the architecture towards web services but this is
unusable. Forcing the users to log in would be a step back in their
eyes too.
Any help would be greatly appreciated.
Leo