This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes Web Services and the fly likes digest value mismatch and disabling pretty printing/formatting of soap message Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "digest value mismatch and disabling pretty printing/formatting of soap message" Watch "digest value mismatch and disabling pretty printing/formatting of soap message" New topic
Author

digest value mismatch and disabling pretty printing/formatting of soap message

Akram Chotu
Ranch Hand

Joined: Apr 18, 2006
Posts: 43
I am trying to validate a signature produced using AXIS+WSS4J client. The validation is performed by using AXIS+WSS4J on the provider side. The signature is performed on the body element in soap message

However during signature validation process I am getting an error "digest value mismatch". I think the message after it is signed is modified and this may be the reason of failure of signature validation.

If I try to print the request soap message using a handler using the api



or using the code



then I am seeing the soap message "somewhat" formatted and printed like this



I am not sure on how AXIS internally representing this soap message when
tranferring on the wire from one to other end but I am looking for below kind of soap message which does not have any indentation, formatting, new lien characters, line feeds, spaces etc.



and since the above soap message does not have any new line characters, line feeds, spaces etc. and so that even if I sign the above message there will not be any formatting issues that may cause the signature validation to fail on the provider end.

Can anyone please tell me how to remove such formatting of soap message and disable pretty printing/formatting of soap messages.
I tried these parameters in both client-config.wsdd on client side and server-config.wsdd on the provider side but no avail.






Thank you in advance.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: digest value mismatch and disabling pretty printing/formatting of soap message
 
Similar Threads
Optional operation parameters (long types)
intermediary adding soap header element breaking signature verification
problem with String [] in axis 1.3 and .net client
Server.userException: Exception while executing Client
Axis Fault: no such operation