Hi all, I have been working with the WSRM implementation of Apache CXF and now I'm combining it with WS-Security. After a struggle the createSequence call is successfully finished with WS-Security added but I am running into a problem with the retransmission. If no acknowledgement is received, the RMS is retransmitting the message with the same timestamp which is causing WS-Security to throw an error regarding a replay attack.
After looking through the internet a bit I found the following post describing exactly the problem that I run into now and how it is solved in Axis2/Sandasha2/Rampart combination (http://wso2.org/library/1027). Then I found the following post on the net where Dennis mentions this problem to Aki ( http://mail-archives.apache.org/mod_mbox/cxf-users/201103.mbox/%3C7b229db0-0865-47ec-8efe-2058b5808177@default%3E ) 'There are some deeper issues here around the way messages are persisted. Right now the message is just captured as sent on the wire. This works fine for plain messages, but once you add in WS-Security the handling needs to change so that the security information (timestamps, in particular) can be updated for each retransmission. That's going to require intercepting the message at a different point in the processing, and persisting in a different form.' In the documentation I found the following statement regarding the control that we have on the order of interceptors. 'The RetransmissionIntercepor will be added on the fly by the RMOutInterceptor so need not appear in your configuration file.' Can maybe someone help me define if this issue has been sovled or addressed in a CXF issue? Or is there some way to force the retransmission interceptor to go through the signing face again without creating multiple signature elements like what the Axis2 solution had? Any help is greatly appreciated. Many thanks in advance. With kind regards, John
