• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

soapUI Mtom enable + signiture = problem

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi ,

I have an mtom web service (data plus attachment).

WhenI sign the request ( with Mtom NOT enabled) with sha1 certificate, certificate works (web service call fails later due to attachment not being mtom). When I enable Mtom I get the following error ( from Layer7 appliance):
Request WSS processing failed: Signature not valid. null
Element #id-FF416124706A221E28145381632108039: Digest value mismatch: calculated: CcL4c1qcfzYWTyQipfSLlSVZ0sw=


Again all non MTOM webservices work and this one works till Mtom enabled = true is set.
All help or ideas greatly appreciated ( tested with same results in soapui 5.00 and 5.2.1 as well as newest paid version)

Sincerely,
glapsvin
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic