You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Dirk Weber <di...@fun.de> on 2009/05/06 10:26:21 UTC
Rampart/C: different policies for inflow and outflow
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
and
return signed WSSE-headers. One single operation must be called with
encrypted
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
to
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,
Dirk
Re: Rampart/C: different policies for inflow and outflow
Posted by Uthaiyashankar <sh...@wso2.com>.
Hi Dirk,
> 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?
With current implementation, it is not possible. There is a jira for
this[1].
Regards,
Shankar
[1] http://issues.apache.org/jira/browse/AXIS2C-619
--
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"