Tuesday, October 13, 2015

WSSecurityEngine: Invalid timestamp The security semantics of the message have expired

This issue normally comes when your Client machine and server machine timing is not in sync. When request reaches to server with different time then server expire the message and sends the same response with error message.
To avoid this error please make sure your client time and server time should be in sync.


Logs:


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode xmlns:ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">ns1:MessageExpired</faultcode><faultstring>The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired)</faultstring></soap:Fault></soap:Body></soap:Envelope>