I think I finally have it working. Not certain it's the ideal solution. But
it works and it took me a long time navigating through the debugger to
figure things out.
My route definition was then
Spoke too soon. It should look something like this:
--
View this message in context:
http://camel.465427.n5.nabble.com/https4-2-15-2-not-recognizing-my-httpClientConfigurer-endpoint-option-tp5767922p5768073.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I just checked the code of your HttpClientconfigurer, you didn’t set the
httpClientBuilder with the SSLConnectionSocketFactory instance that you just
created.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com
My class that implements HttpClientConfigurer now looks like this from your
suggestions: and it still doesn't work.
My createRegistry() looks like this:
@Override
I added a jndi.properties file that looks like this:
My uri now looks like this
It looks like you are not setting the httpClientBuilder argument with your
ssl configuration. Can you have a relook at the method configureHttpClient
you have overridden ?
--
View this message in context:
This still isn't working. It is as though it isn't recognizing my registry
during runtime.
In my unit test I've overrided createRegistry() because I'm not using spring
as your example solution does.
@Override
protected JndiRegistry createRegistry() throws Exception {
JndiRegistry
To do this, I just declare a bean like this:
bean id=allHostname
class=org.apache.http.conn.ssl.AllowAllHostnameVerifier
And then use it on the endpoint like this:
?x509HostnameVerifier=allHostname
Works without any issues.
Ryan
On Fri, Jun 5, 2015, 5:48 PM jspyeatt
Like several similar posts I've seen I need to allow self-signed certs for
https4 (2.15.2). Mine isn't working.
I've created an implementation of HttpClientConfigurer that allows any
host/cert. Below is the implementation of configureHttpClient().
@Override
public void
