Here are two possible explanations for this error message: 1) The "Created" time of the Timestamp was more than 5 minutes ago. This is rejected by default as it is considered "stale". You can change this default via the JAX-WS property "ws-security.timestamp.timeToLive" (which takes a value in seconds).
2) The "Created" time of the Timestamp is more than 60 seconds in the future. You can change the default (60 seconds) via the JAX-WS propertty "ws-security.timestamp.futureTimeToLive". If you want to change the default values for these two properties, you need to change them in the service bean. Colm. On Thu, Jan 10, 2013 at 11:26 PM, fachhoch <[email protected]> wrote: > recently I started getting error > > Invalid timestamp The security semantics of the message have expired > > google search says add ws-security.timestamp.futureTimeToLive" (in > seconds) > > I should add this on server side ?or on client side > I have spring beans for my service and client > > in config to which object should I add this setting. > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Timing-issue-with-WS-Security-tp5721431.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
