you need to make sure that the credentials you?re passing to the end
service are valid for that machine. Unless your web service client is
impersonating a valid user for that end service,
CredentialCache.DefaultCredentials won?t be valid.For example, you can
impersonate it as domain user which also have permission on the end server.
For more information on impersonante, you can refer to:
INFO: Implementing Impersonation in an ASP.NET Application
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q306158
Luke
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026?? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
http://www.microsoft.com/security/security_bulletins/ms03-026.asp and/or to
visit Windows Update at http://windowsupdate.microsoft.com to install the
patch. Running the SCAN program from the Windows Update site will help to
insure you are current with all security patches, not just MS03-026."
Craig - 14 Aug 2003 14:00 GMT
Turns out there was a restart required after setting the ASPNET passwords.
My fault, all is well.
Simply by setting the webservice.Credentials to the DefaultCredentials
allows the public webapp to call the windows auth webservice.
Thanks for you help.
Craig
> you need to make sure that the credentials you?re passing to the end
> service are valid for that machine. Unless your web service client is
[quoted text clipped - 17 lines]
> Update site will help to insure you are current with all security
> patches, not just MS03-026."