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
9 years ago

I think I found a solution (or work-around); I noticed that the request is changing slightly once it leaves SOAP UI:

 

For example the original request may have a field like <payload>cid:147612301643</payload>

 

But after if gets signed it then changes to <payload><inc:Include href="cid:147612301643" xmlns:inc="http://www.w3.org/2004/08/xop/include"/></payload> which fails any hash check on a request since the signed message has been modified.

 

But if you replace the original entry in SOAP UI with the later (from the above examples), the message gets signed as is and passes the hash validation on the target server.

 

Hope this helps,

 

V