Eric's Blog

Day to day experience in .NET
Welcome to Blogs @ IRM Sign in | Join | Help
 Search
Home Blogs

Recent Posts

Tags

Disclaimer

The content of this site is my own personal opinion and does not in any way represent my employer, it's subsideries or affiliates. These postings are provided "AS IS" with no warranties, and confer no rights.

This Blog

Archives

WSE 3.0 and WCF Not Playing Together

I have spend some time trying to get a WSE client to be able to call a WCF service without any satisfying results. Sure there are no problem to get a very basic call to interop with no security by creating a custom binding that uses WS-Addressing specification from August 2004 (see links below). But when I try to add security, for example secure the service with Kerberos I get exceptions. I don't know if I miss something, and please let me know if you have succeeded in getting WCF and WSE to interop with different security scenarios.
I can't find any useful information when googeling either except for this three:
Published den 15 oktober 2007 16:46 by ericqu
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Edouard said:

Have you by chance managed to get that working?

I'm also trying to get a wse 3.0 client call a WCF service without success.

I get an exception when the wse 3.0 client receives the response saying "The signature or decryption was invalid". I don't know what's wrong.

I don't think that comes from the certificate as I managed to call the service with a WCF client.

Thanks for your help

november 20, 2007 18:34
 

ericqu said:

No, I haven't, but I did discover that the SDK contains a sample that could read the WSE 3.0 policy configuration and create the same configuration for WCF. I haven't had the time to try that either though.

november 21, 2007 15:53
 

Edouard said:

Thanks for your answer. I have finally managed to get that working! I used the sample from your first link and as it had been built with a previous release of WCF, I had to modify the data contract attributes to be able to compile (change the MessageMember to MessageBodyMember). But I did not update the service reference after that as I thought that this minor change would not modify the message... There was an incoherence between the client and the service. Simply updating the web reference solved my problem.
november 21, 2007 16:21

Leave a Comment

(required) 
(optional)
(required) 
Submit
Copyright, All rights reserved IRM 2006
Powered by Community Server, by Telligent Systems