axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Weber" <>
Subject Rampart/C: different policies for inflow and outflow
Date Wed, 06 May 2009 08:26:21 GMT
Hi all,

I need to write an Axis2/c / Rampart/C secure web service client to connect
to a 
Jax/WS webservice provided by our customer. All service operations expect
return signed WSSE-headers. One single operation must be called with
SOAP-body but returns a non-encrypted response. According to the configured 
policy, my client correctly send a body-encrypted request, and generates a 
client side SOAP Fault when receiving the response: "FailedCheck/Body need
be encrypted."

My questions are: 
(1) Is there a way to configure different client-side policies for
inflow and outflow? If so, could you give me a hint what I am missing?

(2) If it's not possible, will this be a feature for one of the next 
releases? (forced to ask this ;-)

Sorry, if I missed an appropriate entry in the archive.

Thanks in advance,

View raw message