Hi Dan, In a nutshell, MTOM + WS-Security does not currently work in CXF. When we finish WSS4J 2.0, which will offer a streaming WS-Security implementation as well as the existing DOM implementation, it should be possible to support this in CXF.
Colm. On Thu, Feb 7, 2013 at 7:45 PM, DTaylor <[email protected]> wrote: > Good day, > > The clients we are working on need to be able to send MTOM attachments to > .NET endpoints which are secured. > > Pre-emptively we did some research on CXF with MTOM and WS-Security and > have > found some contradictory information / experiences and I was wondering if > someone could clarify. > > There is an unresolved Jira which seems to indicate the CXF cannot do MTOM > and Signatures at the same time > (https://issues.apache.org/jira/browse/CXF-3687), but that is for CXF > 2.4.1, > we are currently using 2.6.2 and are looking at upgrading to 2.7.2. > > As well, we found this CXF conversation thread > ( > http://cxf.547215.n5.nabble.com/Signature-digest-mismatch-when-NET-supplies-MTOM-attachment-td3270961.html > ) > which seems to indicate that CXF forcibly turns off MTOM when used with a > secure service, causing an incompatability with .NET. Is this still the > case? > > Is there a workaround to use MTOM and WS-Security with CXF & .NET? Or > should it all be working now? > > Just trying to clear up some of our confusion, as some of our projects > claim > to have MTOM and WS-Security working. > > Thanks, > > Dan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/MTOM-Secure-Services-Interop-tp5722891.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
