im trying to send an SOAP-message from an axis2 1.5.4 Client (with Rampart 1.5.1, Tomcat 1.6) to a Websphere Application Server 7. The inquiry is authenticated with a client certificate and the nestet timestamp and the message content itself is signed with the client certificate. That all works fine but i recieve the following error message:
org.apache.axis2.AxisFault: security.wssecurity.WSSContextImpl.s02: com.ibm.websphere.security.WSSecurityException: Exception org.apache.axis2.AxisFault: CWWSS5625E: All the attempts based on each Reference failed. The last exception is: Signature for timestamp found ahead of timestamp. Strict Layout not followed in incoming message. Check that the policy for sending application specifies a Strict layout.: com.ibm.wsspi.wssecurity.core.SoapSecurityException: Signature for timestamp found ahead of timestamp. Strict Layout not followed in incoming message. Check that the policy for sending application specifies a Strict layout. ocurred while running action: com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler$1@696f696f
Can anyone help me to fix this problem? Tank you!
This topic has been locked.
1 reply Latest Post - 2011-07-18T14:20:09Z by DGawron
Pinned topic WS Security, Problem with signing the timestamp of an XML message
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-07-18T14:20:09Z at 2011-07-18T14:20:09Z by DGawron
DGawron 10000054HC50 PostsACCEPTED ANSWER
Re: WS Security, Problem with signing the timestamp of an XML message2011-07-18T14:20:09Z in response to SteffenRehnertIt doesn't sound like you are using Web Experience Factory. Try posting this question to a WebSphere specific forum; you'll get a faster response that way.