Perhaps not a provider being assigned?
Even with a provider assigned I am having the same trouble using the WebServiceClients console sample.
However if I use SoapUI and modify the HTTP Settings, set the Authenticate Preemptively to true and add the aut header I get the correct response. I traced SoapUI through 'Charles' as it allows you to trace though SSL and all looks ok. I asume the header
is missing from the WebServiceClients client proxy request. Below is the good response I got from soap ui with the alice user. If you supply a bad username or passwrd you get HTTP/1.1 401 Unauthorized. If you supply no username or password the you end up with
the empty security contexts.
<ActivityId CorrelationId="9dc8fd05-7bad-47f5-8441-eebc79ced882" xmlns="http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics">374f151f-0f83-498a-bcc5-3fcd48397b09</ActivityId>
It seems I can not get the following parts -
proxyAsmx.Credentials = new NetworkCredential("alice", "abc!123");
to send the correct header request to trigger the 401 and in turn the Module.
proxyWcf.ClientCredentials.UserName.UserName = "alice";
proxyWcf.ClientCredentials.UserName.Password = "abc!123";
What could the issue be here?
I see a possible similar issue @ http://custombasicauth.codeplex.com/Thread/View.aspx?ThreadId=36305
Oddly enough I am also using Vista IIS7 3.5 SP1.
Could there be some security context isue on vista causing an issue?