Contributions
Re: Mtom enable + signiture = problem
Still confused around whether the SOAUP MTOM Client we have 'working' is ACTUALLY Signing the Attachment Or Not ? On the Server side, we're successfully Verifying the SOAP WSSEC Digital Signature passed in, but suspect the Enclosed Attachment is NOT part of the SOAPUI-Generated Signature- in other words, SOAPUI is/can ONLY in effect sign the Body (so the XML Infoset being processed does not include a Base64Binary component representing the attachment) ?? Can SmartBear pls clarify the Signing Attachment Capabilities for MTOM Support in SOUPUI please ?? Regards Gavin Bayfield4.6KViews0likes1CommentRe: Signing soap message mime attachments - problem
Hi, good example of the target Signature format to sign both a msg body and its attachment, but I dont think SOAPUI 'Signature Tab' can add a second<ds:Reference/> element (eg to reference the attachment by cid)- the Parts Table looked like it might have this capability with the "ID" column but I couldnt get it to generate any multi-part messages and cant find any documentation to support this. Happy to be corrected if SOAPUI can do this ?1.9KViews0likes0CommentsRe: Mtom enable + signiture = problem
Yes this helps a Great Deal ! Thanks, this solution works, I find I have to attach the file using the original WSDL format example first in order to set the Attachment Part to the generated partnumber (in example below)147612301643 here: <payload>cid:147612301643</payload> Then once the file is attached, change this line in the request message to the following format (your example correct as is :) <payload><inc:Include href="cid:147612301643" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></payload> DataPower then does then successfully verify the signed message/attachment - Presumably the problem we're fixing is a minor bug in SOAPUI signing-MTOM-attachments, which needs to be addressed in a future release. Many thanks for your speedy reply... Regards Gavin Bayfield4.7KViews1like2CommentsRe: Mtom enable + signiture = problem
Hi I too have in essence the same problem - I can confirm SOAPUI does succesfully sign the SOAP Message Body and DataPower can Verify this message np - however for a MTOM Service setup in SOAPUI this same SOAPUI Digital Signing ONLY works if there is actually NO Attachment included in request message - When MTOM attachment (multipart message_ fails as Hash Values differ ! I suspect this is because SOAPUI is NOT actually Signing the Attachment Part >? Can SmartBear confirm this please ? Does the Professional Version work in this Scenario ? Please Advise ? Thanks & Regards Gavin Bayfield4.8KViews0likes0Comments