If SSL is handled by a load balancer, do I still need to configure it in the WCF serviceCertificate node? My scenario is to use message level security. If someone can explain how load balancing with wcf and ssl works, that would be very nice.
Share
WCF requires security tokens to be passed over a secure transport if the message itself is not signed/encrypted. Since traffic is HTTP between your Big-IP and your individual web servers, you need a way to have security tokens that you know are secured between the client and the Big-IP up front still be passed to your server farm. There’s a couple ways to do that depending on what version of WCF you’re using:
If you’re using WCF 4.0 you can just create a custom binding and set the
AllowInsecureTransportproperty on the built inSecurityBindingElementto signify that you don’t care that the transport isn’t secure.If you’re using WCF 3.5 you have to “lie” about security with a custom
TransportSecurityBindingElementon the server side. You can read my old post about this here.FWIW, they created a hotfix release for 3.5 SP1 that adds the
AllowInsecureTransportto that version, but I don’t know if your company will allow you to install custom hotfixes.