Can't get SSL with X509 working with 1.5.7

[RobertZ]

org.springframework.ws.soap.client.SoapFaultClientException: com.sun.xml.wss.XWSSecurityException: More Receiver requirements [ SignaturePolicy  ] specified than present in the message; nested exception is com.sun.xml.wss.XWSSecurityException: com.sun.xml.wss.XWSSecurityException: More Receiver requirements [ SignaturePolicy  ] specified than present in the message

i know it's an old thread but my solution to the above problem was changing my client policy i was missing the timestamp property.
the server expected a timestamp so the client should add this to the message.

[michal26]

I have been running it on Tomcat 6 and it works fine.

[ramspring]

This is a great blog to understand about the security that can be implemented on WS.

Assuming a scenario server is using Spring-ws WSS4J and Client is totally different may be some other platform other than Spring-ws WSS4J. With this scenario in mind how would the client need to woirk with server.

Or client can just know what the certificate/key is and then establish the communication with the server with client's logic of implementing the security.

One more doubt, if I put the keystore in Webserver/application server itself, does it required to implement this security at application level, assuming the server is dedicated to the specific application.

Since I am in learning stage, I believe the above one is too abstract. Appreciate your response.