WCF cross-domain duplex: your Thawtes

(Ha! see what I did there?)

I have a system whereby a server pushes information from a central DB out to many client DBs (cross-domain via internet), and periodically they call services on the server. This has to withstand intermittent connections, ie queue messages.

I've created a development version using duplex MSMQ that I'm trying to apply transport security. From the reading I've done, it appears that:

• MSMQ uses AD Windows Security, which is irrelevant cross-domain.
• Due to the nature of duplex, each client is effectively a server as well. That means I need to pay $1200 every time I install the system with another client if I want to use SSL.

Are these facts correct? Am I really the only person who needs to secure services that are queued AND cross-domain AND duplex?

You may, in fact, be the only person in the world right now who wants to do this.

Let me embellish.

1. Not many companies are using MSMQ (in the grand scheme of things).
2. Of those that are, the vast majority are using only private queues, a small minority only use public queues.
3. Of those that are, only a handful are using it across the internet.
4. Of those that are, perhaps one is using it to exchange messages in both directions (that would be yours).

But that aside, it seems to me your main challenge will be using MSMQ as a secure transport layer over the internet. Although I have never had to do this, here are a couple of articles:

• http://msdn.microsoft.com/en-us/library/windows/desktop/ms701477(v=vs.85).aspx
• http://msdn.microsoft.com/en-us/magazine/cc164041.aspx

Sorry couldn't be of more help.