| re: default credentials
Which kind of authentication is in place server side ? What is the behavior
if you access the WSDL from your browser ?
AFAIK it won't work when using basic authentication. You can't get the
password when using DefaultCredentials, you just get some kind of hash value
that will allow to get recognized server side (this is why basic
authentication won't work).
--
Patrice
"TrinityPete" <TrinityPete@discussions.microsoft.com> a écrit dans le
message de news:340C1C9D-68F2-4339-B790-A1778FCF3E9C@microsoft.com...[color=blue]
> Hi all,
>
> I have a little problem that is really bugging me. I have a windows forms
> application that calls a web service (VS2005 and Framework 2). As part of[/color]
the[color=blue]
> call to the web service I set the credentials of the webservice proxy to
> System.Net.CredentialCache.Default credentials. The call fails with[/color]
security[color=blue]
> 401. I then change the credentials of the proxy to new NetworkCredential()
> using the same details as I log on to my own machine and the call is OK.
>
> Checking DefaultCredentials in the VS watch window, it looks like username
> password and domain are all empty strings - How can this be?
>
> In the case of defaultcredentials the http logs dont show any username for
> the access, but using the new NetworkCredential the correct username is
> displayed in the log.
>
> ie. Default credentials - no user supplies to IIS
>
> 2006-02-15 14:57:32 W3SVC1 192.168.0.18 POST
> /econntestservice/eConnService.asmx - 80 - 192.168.0.79
>[/color]
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+ Protocol+2.0.50727
..42) 401 2 2148074254[color=blue]
>
> ie. new NetworkCredential - you can see the TRINITY\peterh user
>
> 2006-02-15 14:59:20 W3SVC1 192.168.0.18 POST
> /econntestservice/eConnService.asmx - 80 TRINITY\peterh 192.168.0.79
>[/color]
Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+ Protocol+2.0.50727
..42) 200 0 0[color=blue]
>
>[/color]
| 
