My second article on integrating Windows Communication Foundation with BizTalk Server is now online. The one deals with all the various WCF security configurations and how BizTalk consumes each one.
Specifically, I address message vs. transport security, certificates, username tokens and declarative code-based security. It was pleasing to see how gracefully BizTalk accommodated each security permutation I threw at it.
RSS Feed
Hi Richard, Great series!
I’m struggling a bit with a WCF service that is hosted in a windows service and called from a biztalk orchestration and was hoping perhaps you may have some insight. The only way it will work, on my devlopment server, is to set the Biztalk WCF netTcp transport properties in biztalk to:
Security mode: Transport
Transport client credential type: windows
Transport protection level: EncryptAndSign.
No other security combination works. Why do I have to use this combination?
I’ve checked the config of the WCF service and there are no security/identity entries there. I’d like to test with “none” but it won’t seem to accept that.
Is there something on the service side I have to add in the config? Is it because this is hosted in a windows service?
When I deploy all of this on our build server, the Biztalk WCF netTcp transport properties set like above cause biztalk to just lock up (Running service instance never goes away and CPU goes through the roof). All other Biztalk WCF netTcp transport property combinations on the build server cause an immediate failure like my development box.
Hi Chris,
What error do you get with other security configurations? If you try hosting your service elsewhere (let’s say, self hosting) do you get the same behavior, or have you isolated it to the Windows service?