[CXF-8230] WS-Security and MTOM: Flag org.apache.cxf.ws.security.SecurityConstants.STORE_BYTES_IN_ATTACHMENT not working as expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.2.5
• Component/s: WS-* Components
• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Jochen Riedlinger
• Created: 02/Mar/20 15:18
• Updated: 18/Sep/23 18:51
• Resolved: 03/Mar/20 15:44

Description

Hi,

by default an CXF client that uses MTOM and WS-Security sends the "BinarySecurityToken" and "SignatureValue" elements base64 encoded.

I expect that "BinarySecurityToken" and "SignatureValue" are both sent as attachmentreferenced via XOP:INCLUDE, if I put the flag "org.apache.cxf.ws.security.SecurityConstants.STORE_BYTES_IN_ATTACHMENT=true".
But this does not happen.
If I put STORE_BYTES_IN_ATTACHMENT=true, only the BinarySecurityToken is attached while SignatureValue stays base64 encoded (see attched file "example_request_1.xml").

IMHO the flag should also cause the SignatureValue to attached, shouldn't it?

 

Background story:
The use-case for this is that I want a CXF client to behave like a 3rd party client (SAP) with which we have an compatibility issue.
The SAP client sends BinarySecurityToken, SignatureValue and the real data as MTOM attachment. A CXF client only sends BinarySecurityToken and the real data as MTOM atatchment.

I have the suspision that a CXF service cannot handle a request that sends BinarySecurityToken, SignatureValue and the real data as MTOM attachment.
But since the STORE_BYTES_IN_ATTACHMENT flag does not work as expected, I cannot even write a reproducer....

 

Regards,

Jochen

Issue Links

• depends upon: WSS-666 Support processing SignatureValue bytes stored in attachments