This project is read-only.

If You Need to Support legacy WSE Clients Then Use a CustomBinding in WCF

- J.D. Meier, Carlos Farre, Jason Taylor, Prashant Bansode, Steve Gregersen, Madhu Sundararajan, Rob Boucher

If you have WSE client base, you will need to use a custom binding in your service, to support WSE legacy clients. This will provide interoperability for the existing clients, without requiring clients to migrate to WCF. Here’s a mapping of the WSE bindings to WCF bindings elements:

anonymousForCertificateSecurity anonymousForCertficate.
kerberosSecurity or mutualCertificateSecurity11 MutualCertificate.
usernameOverTransportSecurity UserNameOverTransport
usernameForCertificateSecurity usernameForCertificateSecurity

To create a custom binding to support WSE clients:
  1. Add a customBinding to your WCF service.
  2. Specify a name for your customBinding.
  3. Specify an authentication mode that maps to the authentication used in your old WSE service:
  4. Specify that the August 2004 version of the WS-Addressing specification is used by WCF
  5. Configure the WCF endpoint to use the custom binding

Additional Resources

For detailed information on how to configure the customBinding, see “How to: Configure WCF Services to Interoperate with WSE 3.0 Clients” at

Last edited Jun 12, 2008 at 8:23 PM by prashantbansode, version 1


No comments yet.