Pablo M. Cibraro (aka Cibrax)

I have recently published an article describing a WS-I18N implementation for WCF in "The Code Project" web site.

In my opinion, the parameterized queries approach is always better than the traditional approach of joining string to build a dynamic SQL string.

I updated the WS-Compression code to make it work with the latest WCF release.

I finally decided to publish a STS implementation for WCF.  (It is based on one of my previous posts, "Implementing a Secure token service with WCF")

This post discusses first the most important aspects to consider regarding security, and then, how these aspects are implemented with web services.

What certificate to use or where to get one of these, is perhaps is one the most common question I read often in the MS newsgroups.
Well, for starters, there are many kinds of X509 certificates around, each one for a different purpose. And to make the matters worse, each vendor offers similar certificates with different names.
Verisign, RSA, Thawte and others usually offer certificates for the following purposes:

William Tay (Aka Softwaremaker) one of the most  knowledgeable WSE guys around has published an excellent article about interoperability between WSE 2.0 and WCF.
I usually find people concerned about topics like this, the different interop issues between WSE 2.0, WSE 3.0 and WCF. 
Well, this article really helps clarify the required points to make both products work together. In addition, it includes some code samples.

Today I found this interesting blog entry to making WSS4J (Axis) work with WSE 3.0 using a Mutual X509 scenario (There are two certificates, the first one for client authentication and the second one for message protection).
Since WSE 3.0 and WCF are compatible at wire level (I have already developed a sample to show this), this entry is also useful for interop testing between WCF and WSS4J.