Dennis, I am a colleague of Ramzi's. It turns out that WS-SecureConversation was not an actual requirement. We were able to ask the .NET team who owns the service to turn it off. We also removed the interceptors as you recommended. We managed to invoke the service after making those two changes.
I just wanted to thank you for providing the key insights. Pohl Longsine On 7/30/14 6:59 PM, "Dennis Sosnoski" <d...@sosnoski.com> wrote: >Hi Ramzi, > >There are issues in combining WS-SecureConversation with >WS-ReliableMessaging in the 3.0.x release. All information in this message is confidential and may be legally privileged. Only intended recipients are authorized to use it.
