In terms of a workaround, yes you should be able to subclass the WSS4J interceptors and override AbstractWSS4JInterceptor.loadCryptoFromPropertiesFile with the fix that I committed to WSS4J.
Colm. On Fri, Oct 20, 2017 at 9:21 AM, Colm O hEigeartaigh <cohei...@apache.org> wrote: > The fix will be in releases 2.0.11, 2.1.12, 2.2.1 - WSS4J 1.6.x is no > longer maintained. > > Colm. > > On Thu, Oct 19, 2017 at 6:06 PM, pra...@tracelink.com < > pra...@tracelink.com> wrote: > >> Colm, that's great! Can you please let me know when this would be >> available >> for use? Will it be made available via maven? Is it a wss4j 1.6.19 fix? >> >> Unfortunately, I cannot upgrade to the latest versions of cxf because we >> support sdk code given to us which was written a long time ago. >> >> Much appreciate the quick response. IS there some work-around for this >> specific issue or not really? >> >> Thanks, >> PR >> >> >> >> -- >> Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html >> > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
