Forum Discussion

glapsvin's avatar
glapsvin
New Contributor
9 years ago

Mtom enable + signiture = problem

Hi , I have an mtom web service (data plus attachment). WhenI sign the request  ( with Mtom NOT enabled) with sha1 certificate certificate works (ws fails later due to attachment not being mtom)....
varias's avatar
varias
New Contributor

Hi,

 

I have pretty much the same issue. I have an MTOM (enabled) attachment in a request where I am using a signiture as authentication.

 

I get an error of "hash values do not match" on the server I am connecting to which means that the request was altered after the request was digitally signed.

 

I think SOAP UI is signing the request and then altering the request in some way when setting up the request with the MTOM attachment.

 

This error does not occur when the attachment is imbeded into the request. Only when the attchament is MTOM enabled and the request digitally signed.

 

Hopefully there is a solution or some setting I am missing.

 

Thanks,

 

V

 

 

grb123's avatar
grb123
New Contributor
9 years ago

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 Bayfield