This is a bug in WSS4J which I've fixed:
https://issues.apache.org/jira/browse/WSS-594
Colm.
On Thu, Nov 17, 2016 at 6:01 PM, Martin Fernau
wrote:
> I was able to fix this by adding my own AbstractSoapInterceptor and
> manually adding the mustUnderstand-Attribute
I was able to fix this by adding my own AbstractSoapInterceptor and
manually adding the mustUnderstand-Attribute to the EncryptedHeader
Element and set it to "true".
After this the remote server accept my messages.
Thanks - solved!
Am 16.11.2016 um 15:39 schrieb Martin Fernau:
Hi Colm,
Hi Colm,
thanks for your response. I finally got a maybe valuable information
from the distributor of this service.
They found the following information in their logs:
--cut
Message authentication failed.
Service:
https://www.fhdsales.dealerconnection.com/DMSInterface/V4/ServiceCustomer.svc
As I'm still stuck in this I'm going to post WSDL and examples in hope
someone can point me to the right direction.
The problematic method is "InsertCustomer". Other methods work! I guess
its related to the additional header for the InserCustomer method which
I add as follows:
-cut
Hello,
this thing is a real problem and I need it to bring to work...
I need to consume a third party web service (implemented in .NET hosted
by IIS) using ws-policy/ws-security.
Basically the client works and I can successfully call some methods. But
for one method the call fails with "An