When you say the message is encrypted, what does it look like? If it is secured using WS-Security, then you need to set up the configuration to handle this. The "tlsClientParameters" config only works for transport layer security...
Colm. On Fri, Apr 17, 2015 at 6:22 PM, sagarsoni89 <[email protected]> wrote: > Dear all, > > I am invoking a secured SOAP WebService (HTTPS) using Camel CXF deployed in > Fuse. In the client, we have configured TrustStore and Keystore as per the > standard config (Http-conduit). We're able to hit the server via Netscaler. > The server is generating the response and sending it back to Netscaler. > > When the response is received from Netscaler, it is encrypted and should be > decrypted by Camel CXF. The decryption is not happening and on the client > we > get a parsing error since the response is all encrypted. > > Any clues of what could be the problem ? > > this is my ws client config > > <http:conduit name="*.http-conduit"> > <http:tlsClientParameters> > <sec:keyManagers keyPassword="******"> > <sec:keyStore file="<keystore>.jks" password="******" > type="JKS"/> > </sec:keyManagers> > <sec:trustManagers> > <sec:keyStore file="<keystore>.jks" password="******" > type="JKS"/> > </sec:trustManagers> > <sec:cipherSuitesFilter> > <sec:include>.*</sec:include> > </sec:cipherSuitesFilter> > </http:tlsClientParameters> > </http:conduit> > > > Thanks > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-not-decrypting-SOAP-Response-tp5756221.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
