wood burning stoves 2.0*
The moose likes Web Services and the fly likes Rampart sample not encrypting soap message Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Rampart sample not encrypting soap message" Watch "Rampart sample not encrypting soap message" New topic
Author

Rampart sample not encrypting soap message

Alan Richardson
Greenhorn

Joined: Mar 05, 2007
Posts: 17
Hello all,

In need to encrypt the body of SOAP messages on a service. I'm using Axis2 so therefore I'm working through some of the Rampart examples to try and understand how it can be applied in Axis.

Sample 03 is perhaps the closest to what I want to do, so I'm focusing on that. However I can't seem to get it to work correctly. As I understand it the message sent to the service should have an encrypted body, correct? (the RecipientToken has a X509Token, and <body/> is specified in the encryptedParts element).

The readme/policy files are here: https://svn.apache.org/repos/asf/webservices/rampart/trunk/java/modules/rampart-samples/policy/sample03/

The security header is included in the message, the service is invoked and no errors are thrown *but* I'm not seeing an encrypted body in SOAP Monitor and I'm not sure why. Any ideas what might be going on here?

Here is the request message (how I'm seeing it in SOAP Monitor) (I've cut the <CipherValue> short to make it more readable):




This is how I'm invoking the service:



[ September 11, 2007: Message edited by: Alan Sunley ]
[ September 11, 2007: Message edited by: Alan Sunley ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Rampart sample not encrypting soap message
 
Similar Threads
intermediary adding soap header element breaking signature verification
Rampart encrypting options: I can't encrypt parameters
error while recieving a signed response
WS-Security with XWSS and SoapUI
Configuring the SOAP Header in client