I have a SOAP Endpoint on my web service that uses SOAP Security.
During the transition to daylight saving time this spring, my service went down with the error:
com.sun.xml.wss.impl.WssSoapFaultException: The creation time is older than currenttime - timestamp-freshness-limit - max-clock-skew; nested exception is com.sun.xml.wss.XWSSecurityException : com.sun.xml.wss.impl.WssSoapFaultException: The creation time is older than currenttime - timestamp-freshness-limit - max-clock-skew
The request that caused the crash had a soap header that was created at 2017-03-26T04:00:2.290Z, and the error logged on the server has the timestamp: 2017-03-26 05:00:02,417 (exaclty one hour difference - likely dst related)
Is this a known issue with SOAP Security? Has anyone encountered this before and figured out a solution?