Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Interop
Wednesday, September 09, 2009 8:57 AM

WWSAPI to WCF interop 11: security binding templates

In my previous post on WsUtil , I explained how the generated helper functions can simplify the creation of WS_SERVICE_PROXY and WS_SERVICE_ENDPOINT. In both of these functions, the first parameter is a pointer to a same binding template. When no security
Posted by haoxu | 0 Comments
Friday, June 26, 2009 2:32 PM

WWSAPI to WCF interop 10: WsUtil.exe, the silver bullet

In my previous post on interoperating with WCF BasicHttpBinding endpoint , I explained that you had to set the channel properties to match SOAP version and addressing version on the server side. Wouldn’t it be great if you don’t have to do all that? That’s
Posted by haoxu | 0 Comments
Friday, June 26, 2009 2:10 PM

Common WWSAPI errors: addressing version mismatch

WWSAPI supports two WS-Addressing versions: the existing W3C recommendation version ( 1.0 ) and the older 2004/08 version ( 0.9 ). WS-Addressing defines a set of SOAP headers to describe the message recipient, targeted action and some other basic messaging
Posted by haoxu | 1 Comments
Thursday, June 25, 2009 4:14 PM

Common WWSAPI errors: SOAP version mismatch

There are two versions of SOAP supported by WWSAPI and most other web services stacks: SOAP 1.1 and SOAP 1.2 . Although the basic message layout in the two SOAP versions is the same (Header and Body inside Envelope), there are three main differences:
Posted by haoxu | 0 Comments
Monday, May 18, 2009 12:11 PM

More on HTTP header authentication

My previous post on header authentication comparison between WWSAPI and WCF mentioned the impersonation level. Here is a bit more detail as people still seem to be caught by surprise due to this difference. I mentioned that WCF client could set the impersonation
Posted by haoxu | 1 Comments
Friday, May 15, 2009 10:52 AM

WWSAPI to WCF interop 9: secure conversation bootstrapped by Kerberos AP-REQ token

In my post on WWSAPI federation support , I explained how to set up secure conversation on the WWSAPI client to work with a WCF server using WSFederationHttpBinding. In this post, I’ll show how to use secure conversation without federation. Secure conversation
Posted by haoxu | 1 Comments
Monday, April 27, 2009 11:55 PM

WWSAPI to WCF interop 8: invalid XML characters (part 2)

In part 1 of this topic, I explained that some Unicode characters would be rejected by WWSAPI’s XML reader and writer because they are not considered legal in XML spec. There is an XML reader property and an XML writer property to allow such characters.
Posted by haoxu | 1 Comments
Wednesday, April 22, 2009 10:36 AM

WWSAPI to WCF interop 8: invalid XML characters (part 1)

Although all Unicode characters can be carried in XML document, not all characters are considered legal according to XML 1.0 spec , the version used by SOAP and supported by WWSAPI. As you can see in the production copied below, ASCII characters under
Posted by haoxu | 2 Comments
Thursday, April 09, 2009 1:05 AM

403 Forbidden due to client certificate issue

Just when I thought I had seen all possible 403 Forbidden errors and could pinpoint the 403 issues without looking into traces, I found myself surprised by another 403 error. I was testing a WWSAPI client to WCF server interop scenario. Only this time
Posted by haoxu | 1 Comments
Friday, March 27, 2009 12:31 AM

WWSAPI to WCF Interop 7: HTTP header authentication (part 3) - used in BasicHttpBinding with transport credential only

In my previous post I explained how to do HTTP header authentication protected by SSL in WWSAPI. In this post, I’ll show how to do header authentication without SSL. In WCF, this mode is called TransportCredentialOnly and is only available in BasicHttpBinding.
Posted by haoxu | 0 Comments
Wednesday, March 25, 2009 12:07 AM

WWSAPI to WCF Interop 7: HTTP header authentication (part 2) - used in WSHttpBinding with transport security

In WCF’s standard bindings, HTTP header authentication can be used in WSHttpBinding with security mode Transport. In this security mode, the client credential type can be set to either Basic, Digest, Ntlm or Windows (Negotiate scheme) to enable HTTP header
Posted by haoxu | 2 Comments
Friday, March 13, 2009 11:50 PM

WWSAPI to WCF Interop 7: HTTP header authentication (part 1) - comparison

Just like WCF, WWSAPI supports Basic, Digest, NTLM and Negotiate HTTP header authentication (If you are not familiar with HTTP header authentication, you can read more details about it at Nicholas Allen’s HTTP authentication post ). The two implementations
Posted by haoxu | 2 Comments
Tuesday, December 02, 2008 10:55 AM

WWSAPI to WCF interop 6: NetTcpBinding with transport security

NetTcpBinding provides a more efficient way to send/receive SOAP messages than HTTP does. The SOAP envelopes are transferred in binary format and an XML dictionary is built over the TCP session to help further reduce the payload size. NetTcpBinding supports
Posted by haoxu | 3 Comments
Monday, November 24, 2008 10:43 AM

WWSAPI to WCF interop 5: WSFederationHttpBinding with mixed mode security

WCF endpoints with WSFederationHttpBinding accept SAML tokens issued by trusted Security Token Services (STS, the Issuing Party, or IP). The first thing that should be noted with WSFederationHttpBinding is that secure conversation (specifically, the February
Posted by haoxu | 3 Comments
Tuesday, November 18, 2008 11:49 AM

WWSAPI to WCF interop 4: WSHttpBinding with username over transport security

WWSAPI doesn’t support full message mode security (where security negotiation happens at SOAP message level and parts of the envelope are signed and encrypted using XML signature and XML encryption) in Win7 time frame. This means the default WSHttpBinding
Posted by haoxu | 3 Comments
More Posts Next page »
 
Page view tracker