<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>ControlSystemWorks Blog - msmq</title>
    <link>http://www.controlsystemworks.com/blog/</link>
    <description>Of CSWorks and software development</description>
    <language>en-us</language>
    <copyright>ControlSystemWorks.com</copyright>
    <lastBuildDate>Tue, 29 Sep 2009 04:52:32 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.3.9074.18820</generator>
    <managingEditor>support@ControlSystemWorks.net</managingEditor>
    <webMaster>support@ControlSystemWorks.net</webMaster>
    <item>
      <trackback:ping>http://www.controlsystemworks.com/blog/Trackback.aspx?guid=8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa</trackback:ping>
      <pingback:server>http://www.controlsystemworks.com/blog/pingback.aspx</pingback:server>
      <pingback:target>http://www.controlsystemworks.com/blog/PermaLink,guid,8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa.aspx</pingback:target>
      <dc:creator>Sergey Sorokin</dc:creator>
      <wfw:commentRss>http://www.controlsystemworks.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
While working on one of my projects, I had to make WCF run over a farm of load-balanced
message queues. After several days of web search, asking questions and coding I have
come up with the following "Step-by step guide for setting up certificate security
for WCF over MSMQ communication". 
</p>
        <p>
The goal is to implement a secured WCF communication based on MSMQ under the following
requirements/assumptions/recommendations. 
</p>
        <ul>
          <li>
All MSMQ traffic must be encrypted and signed.</li>
          <li>
No involvement of Windows Domain security and Active Directory.</li>
          <li>
No code changes required on the client or on the server side.</li>
          <li>
MSMQ version 4.0 (W2K8) is used, but it would be nice to have a solution that works
on MSMQ 3.0 (W2K3) as well.</li>
          <li>
There must be a well-established and straightforward routine for setting up secured
communication that can be followed during test/staging/production deployment.</li>
        </ul>
        <p>
The weapon of choice is message-based certificate security. To put it simple, it means
two things: 
</p>
        <p>
        </p>
        <li>
all security-related activities happen on WCF level, MSMQ engine works only as a transport;</li>
        <li>
certificate keys are stored on client and server machines.</li>
        <p>
          <a href="http://www.controlsystemworks.com/articles/CertificateSecurityForWcfOverMsmq.html">Read
on...</a>
        </p>
        <img width="0" height="0" src="http://www.controlsystemworks.com/blog/aggbug.ashx?id=8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa" />
      </body>
      <title>Certificate security for WCF over MSMQ communication</title>
      <guid isPermaLink="false">http://www.controlsystemworks.com/blog/PermaLink,guid,8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa.aspx</guid>
      <link>http://www.controlsystemworks.com/blog/2009/09/29/CertificateSecurityForWCFOverMSMQCommunication.aspx</link>
      <pubDate>Tue, 29 Sep 2009 04:52:32 GMT</pubDate>
      <description>&lt;p&gt;
While working on one of my projects, I had to make WCF run over a farm of load-balanced
message queues. After several days of web search, asking questions and coding I have
come up with the following "Step-by step guide for setting up certificate security
for WCF over MSMQ communication". 
&lt;/p&gt;
&lt;p&gt;
The goal is to implement a secured WCF communication based on MSMQ under the following
requirements/assumptions/recommendations. 
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
All MSMQ traffic must be encrypted and signed.&lt;/li&gt;
&lt;li&gt;
No involvement of Windows Domain security and Active Directory.&lt;/li&gt;
&lt;li&gt;
No code changes required on the client or on the server side.&lt;/li&gt;
&lt;li&gt;
MSMQ version 4.0 (W2K8) is used, but it would be nice to have a solution that works
on MSMQ 3.0 (W2K3) as well.&lt;/li&gt;
&lt;li&gt;
There must be a well-established and straightforward routine for setting up secured
communication that can be followed during test/staging/production deployment.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
The weapon of choice is message-based certificate security. To put it simple, it means
two things: 
&lt;p&gt;
&lt;li&gt;
all security-related activities happen on WCF level, MSMQ engine works only as a transport;&lt;/li&gt;
&lt;li&gt;
certificate keys are stored on client and server machines.&lt;/li&gt;
&lt;p&gt;
&lt;a href="http://www.controlsystemworks.com/articles/CertificateSecurityForWcfOverMsmq.html"&gt;Read
on...&lt;/a&gt; 
&lt;/p&gt;
&lt;img width="0" height="0" src="http://www.controlsystemworks.com/blog/aggbug.ashx?id=8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa" /&gt;</description>
      <comments>http://www.controlsystemworks.com/blog/CommentView,guid,8ebcd9ee-d6b3-48a2-9a0c-789bada4a4fa.aspx</comments>
      <category>msmq</category>
      <category>security</category>
      <category>wcf</category>
    </item>
  </channel>
</rss>