You are sending multiple messages with the same Timestamp, and the service endpoint is treating it as a message replay attack. Your options are:
a) Generate a unique timestamp per-request (recommended) b) Disable replay attack detection on the service side (not recommended), by setting the JAX-WS property "ws-security.enable.timestamp.cache" to "false". Colm. On Wed, May 28, 2014 at 11:27 AM, Alexander Savinov <[email protected]>wrote: > I am using WSS4J 2.0 to create the SecurityHeader. > I have created the Timestamp, it looks correct. > > <wsu:Timestamp wsu:Id="TS-125be995-154f-4da5-807c-72059bd69a6b"> > <wsu:Created>2014-05-28T10:23:38.747Z</wsu:Created> > <wsu:Expires>2014-05-28T10:28:38.747Z</wsu:Expires> > </wsu:Timestamp> > > Time in my timezone is 12:24, but this shouldn`t matter if i understood > correct, but i am getting an Exception. > > Invalid timestamp: A replay attack has been detected > > Can somebody help me with this issue or give a hint. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
