[CXF-6443] CXF streaming-enabled web service cannot process MTOM/XOP-optimized content within a CipherValue element

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.5
• Fix Version/s: 3.2.5
• Component/s: WS-* Components
• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Dallas Vaughan
• Created: 05/Jun/15 15:43
• Updated: 25/Mar/19 12:28
• Resolved: 01/May/18 13:42

Description

The DOM-based fix for this issue was implemented for CXF-6409

When a CXF WS-Security streaming-enabled web service endpoint is configured to use WS-Security and MTOM, CXF cannot handle requests from .NET and Metro clients because it cannot process xop:Include elements that are children of enc:CipherValue elements, as both of these clients will optimize any large encrypted (base64-encoded binary) content by serializing it as a MIME part.

For example, when a Metro MTOM-optimized WS-Security-based request is sent to a CXF endpoint, the following exception is thrown within org.apache.xml.security.stax.impl.processor.input.AbstractDecryptInputProcessor$DecryptionThread.run():

org.apache.xml.security.exceptions.XMLSecurityException: Unexpected StAX-Event: START_ELEMENT

Issue Links

• relates to: SANTUARIO-484 Support processing MTOM/XOP-optimized content within a CipherValue element for StAX implementation
• relates to: WSS-628 Support processing xop:Include for the streaming WS-Security stack