Our service also requires Windows authentication, but of course it authenticates against an AD located centrally with us. In other words, two completely separate user stores are used for the two types of authentication. Is there no way around this limitation?

What we don’t know is whether the clients will be willing to save their credentials and thus be able to use the default proxy server. It seems like a smart thing to do given the limitations, but we don’t have a strong enough survey of customer environments to know for sure.

We’ve put together the steps to prompt for credentials, but where do we put them? We’re already filling ClientCredentials.UserName with the credentials to our server, and even though it’s not Basic Auth, we feel kind of stuck. I’ve spent alot of time digging through the ServiceModel library with Reflector and am a bit disappointed with how HttpChannelFactory.CreateAndOpenTokenProvidersCore was implemented. If you had left anything in there that would have allowed me to write a custom SecurityTokenProvider I’d do that, but the SecuritTokenRequirement for both is so similar it doesn’t look like that would work.

Andrew

WCF does not need to be used to provide credentials to the HTTP web proxy. Instead let the binding object use the default web proxy (it does so by default), and enable the supplying of the user’s default credentials for proxy server authentication by adding the following to your client app’s App.Config file:-

The fact that using the user’s default credentials for proxy auth is disabled by default is what trips up so many people. And it’s quite hard to enable it in code; the best place is in the XML config file.

For further reference, see here:-
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2497236&SiteID=1

Andrew

What is the situation in the .NET 3.5 version of WCF?

Thanks, Andrew

I have problem getting through my proxy using a WCF client and calling a WCF service.

The proxy server uses windows authentication (different windows domain than client) and the WCF service uses username token.

The service is being hosted in IIS and am using basicHttpBinding.

I have tried many combinations and none seem to work. Can’t get past the proxy with 407, proxy authentication required.

My code looks like this:

// username token credentials
math.ClientCredentials.UserName.UserName = @”TheUser”;
math.ClientCredentials.UserName.Password = “Mickey1″;

// proxy credentials
math.ChannelFactory.Credentials.Windows.ClientCredential = new System.Net.NetworkCredential(“domainuser”, “password”, “domainname”);

// call method now ….

My configuration looks like this:

Any help would be greatly appreciated it.

Regards,
Sergio