This week's book giveaways are in the Cloud and AI/ML forums.
We're giving away four copies each of Cloud Native Patterns and Natural Language Processing and have the authors on-line!
See this thread and this one for details.
Win a copy of Cloud Native PatternsE this week in the Cloud forum
or Natural Language Processing in the AI/ML forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

Problem with MTOM attachment in secured WS

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Short story:
I've got a problem with calling secured WS when attachment is in MTOM mode. Digest of request and one calculated on server side don't match.
I use soapUI 4.5.1. Digest alghorithm is default (although I tried all of them).

Long story:
Enviroment description:
WS (Axis2 1.6.2) secured with Rampart allowed to recieve MTOM attachements.
SoapUI request settings:
Enable MTOM: true
Force MTOM: true
Pretty print: false
Strip whitespaces:true

SoapUI Outgoing WS-Security Configuration:
Timestamp+Signature (in that order)

Key Identifier Type: Binary Security Token
SA, SC and DA - default
Use single certificate: checked
Parts are empty

I have followed instructions from this topic ( but with no positive result.

Any idea why?

Best regards.


Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Did you solve the problem? i have a problem with soapUI 4.5.1 using a mockedService that has to support MTOM and ws security.
also the latest snapshot (January 2013) does not work.

a non MTOM message works, with MTOM:
Tue Jan 08 12:21:35 CET 2013:ERROR:An error occured [Missing operation for soapAction [...] and body element [{...}EncryptedData] with SOAP Version [SOAP 1.1]], see error log for details

the error log only shows details..

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!