Thank You Colm, I'll pull together a test for you to run - to demonstrate what I'm seeing. Our thinking here - is that the CXF: SecureConversationTokenInterceptorProvider.setupClient - pulls over too many properties - it's call to: mapSecurityProps().
We can workaround - by clearing some keys out - in our own IssuedTokenInterceptor. But I will pull together an example for you - that I hope will make discussing this easier. Talk Soon F Layout of test - attached. <http://cxf.547215.n5.nabble.com/file/n5746287/imageCXFOverview.jpg> -- View this message in context: http://cxf.547215.n5.nabble.com/CXF-SecureConversationTest-Fails-to-renew-SCT-no-examples-or-tests-tp5746139p5746287.html Sent from the cxf-dev mailing list archive at Nabble.com.
