0

I am architecting a solution that will use WCF to make all the computers in my organization periodically "call home". Let's suppose for the sake of discussion that each computer in my organization has a weather sensor connected to it. The purpose of this application is that each computer should contact a central server to report what the weather is in its location. The data to be transmitted is encoded as a string.

Suppose for the sake of discussion that I have a Windows Service which invokes a method SendWeatherReport once a day. The signature of this function is:

void SendWeatherReport(string report);

Suppose that I have set up a WCF method with the following interface:

[ServiceContract]
public interface IWeatherReportReceiver
{
    [OperationContract]
    void GetReport(string report);
}

I have the following requirements:

1) My weather report information is proprietary and confidential; it must be encrypted for security purposes.

2) The weather report information will be transmitted over the internet. The computer running the WCF service to receive the report will be at example.com.

3) The weather report must get past some over-zealously configured firewalls on its way to the server.

Now that I've explained my requirements, please explain to me how I can set up my endpoint configuration to meet these requirements.

To satisfy (1), I believe that I will need to use the net tcp binding. For (3), perhaps I can configure this binding to work on port 80, 443, or some other commonly used port. My primary concern here is that I don't know how to configure the software to identify itself to the WCF server...

Vivian River
  • 31,198
  • 62
  • 198
  • 313
  • You don't have to use tcp binding. A http binding using transport security will encrypt your data. But you will need an SSL certificate for your server side. This is also less likely to be blocked by a firewall, because it is standard https. – Hinek Nov 30 '11 at 16:10

2 Answers2

3

WsHttpBinding can encrypt message, even without https.

You have to create Binding with SecurityMode="Message" if you want to use SOAP encryption, or SecurityMode="Transport" if you want (and can) use https Take a look at How to: Set the Security Mode

My feeling is that using an HTTP protocol will be far more simplier to deploy thant binary TCP, as proxies often only allows http traffic.

Concerning the authentication, it depends :) The most secure mechanism is to use client certificate, but do you need it versus a standard user/password authentication ? (and all its infrastructure required to work)

Steve B
  • 36,818
  • 21
  • 101
  • 174
  • Thanks for your answer! I tried using the wsHttpBinding, and I got an error message. It says: `The caller was not authenticated by the service.` The machines that "call home" will not be using the same logon credentials as the server, so it is important that they be able to talk somehow. Perhaps some SSL certificates are in order... – Vivian River Nov 30 '11 at 16:43
  • Configuring WCF is often a question patience. You have to make matching the settings in IIS, the settings in the server conf and the settings in the client app. Not always trivial. One suggestion, try to navigate to the svc file (if you are using one) with your browser. If everything is ok, you will see a good message, if not, an error message will appear to help you solving the issue. – Steve B Nov 30 '11 at 17:50
2

Sounds like the perfect application for Microsoft's Service Bus.

JohnC
  • 844
  • 4
  • 10