Skip navigation

7 Replies Latest reply on Nov 15, 2012 9:48 PM by ffang

http:conduit not used for HTTPS

muruga.mani Nov 13, 2012 10:31 AM

<http:conduit name="*.http-conduit">

<http:tlsClientParameters secureSocketProtocol="SSL">

<sec:keyManagers keyPassword="xxxxxx">

<sec:keyStore type="JKS" password="xxxxx" file="C:/Temp/testcert.jks" />

</sec:keyManagers>

<sec:trustManagers>

<sec:keyStore type="JKS" password="xxxxx" file="C:/Temp/testcert.jks" />

</sec:trustManagers>

<sec:cipherSuitesFilter>

<sec:include>..</sec:include>

</sec:cipherSuitesFilter>

</http:tlsClientParameters>

<http:client AllowChunking="true"/>

</http:conduit>

I have to consume a HTTPS webservice and with the http:conduit above, I couldn't really invoke the secured webservice. I have to use the JVM parameters in order to invoke the webservice.

Any thoughts on what is missing here.

1. Re: http:conduit not used for HTTPS

ffang Nov 13, 2012 7:15 PM (in response to muruga.mani)

Hi,

Seems the http:conduit not get picked up by cxf bus.
Could you elaborate how you use cxf client and the whole configuration? Also the FUSE ESB version? And how you configured the JVM parameters?

Do you see any exception in log around cxf bus loading?

Freeman
Actions
2. Re: http:conduit not used for HTTPS

muruga.mani Nov 14, 2012 11:32 AM (in response to ffang)

Here is the camel context that is being used. I haven't put this in the ESB yet. I am using the camel-context to start the process and testing out.

I would have set the JVM parameters at the instance properties file if I had to.

The FUSEESB we have is 7.0.2 (But this is not deployed in the Fuse ESB yet as it fails in the local testing).

Thank you and really appreciate all the help that you are providing.
Actions
3. Re: http:conduit not used for HTTPS

ffang Nov 14, 2012 7:11 PM (in response to muruga.mani)

Hi,

The camel router is your service part, right?
I'd like to see your whole client side configuration which need load the http:conduit.

Freeman
Actions
4. Re: http:conduit not used for HTTPS

muruga.mani Nov 15, 2012 3:06 PM (in response to ffang)
Thank you for all your help!

Please find the attached camel config file.

camel-config.xml 4.7 KB
Actions
5. Re: http:conduit not used for HTTPS

ffang Nov 15, 2012 7:49 PM (in response to muruga.mani)

Hi,

So you hope the
this endpoint has nothing to do with cxf and http:conduit is cxf specific configuration, you need a camel-cxf provider endpoint which can pick up cxf http:conduit configuration and call the https://asfdasdf.adf.asf.asdf:5618/Reservation

Freeman
Actions
6. Re: http:conduit not used for HTTPS

muruga.mani Nov 15, 2012 9:35 PM (in response to ffang)

Thanks for your response. I was thinking that it can pick up as it is configured for the wild card match and we have the https URL.

Can you please guide me on how to utilize the certificate to invoke the https URL through camel. I would really appreciate your help. Thanks again for all your help.
Actions
7. Re: http:conduit not used for HTTPS

ffang Nov 15, 2012 9:48 PM (in response to muruga.mani)

Hi,

Besides use camel-cxf provider which can pick up the cxf configuration http:conduit, you can also use camel-http provider to do it, need set up SSL for http client, take a look at
to get more details.

http://camel.apache.org/http.html

Freeman
Actions

Go to original post