Hi Freddy, The patch looks fine - can you create a new JIRA + attach the patch there? Two things of note:
a) You've removed the existing behaviour of "signing with the token" for renewing...is the response secured in any way? b) There looks to be a lot of duplicate code between the issue + renew operations in the SecureConversationInInterceptor Colm. On Wed, Feb 25, 2015 at 9:20 PM, Freddy Exposito <[email protected]> wrote: > Hi Colm, > > This patch works for us. > > renew-in-secure-conversation.patch > < > http://cxf.547215.n5.nabble.com/file/n5754615/renew-in-secure-conversation.patch > > > > Not sure why SecurityContextToken constructor doesn't set the ID when > receiving uuid; that's why I added > > > sct.setID(WSSConfig.getNewInstance().getIdAllocator().createSecureId("sctId-", > sct.getElement())); > > Thanks, > Freddy > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SCT-Renew-in-Secure-Conversation-tp5754498p5754615.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
