Version 3.0.1 and 3.0.2 does not work with "UntrustedSSL" context #895

olivier-schmitt opened this Issue Nov 23, 2016 · 6 comments


None yet

5 participants



This code :

Config config = Config.DEFAULT;
IOSClientBuilder.V2 v2 = OSFactory.builderV2()
return v2.authenticate();

Works fine with 3.0.0 but does not work with 3.0.1 & 3.0.2 :

Exception in thread "main" ConnectionException{message=peer not authenticated, status=0}
at org.openstack4j.connectors.resteasy.HttpExecutorServiceImpl.invoke(
at org.openstack4j.connectors.resteasy.HttpExecutorServiceImpl.execute(
at org.openstack4j.core.transport.internal.HttpExecutor.execute(
at org.openstack4j.openstack.internal.OSAuthenticator.authenticateV2(
at org.openstack4j.openstack.internal.OSAuthenticator.invoke(
at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(
at org.openstack4j.openstack.client.OSClientBuilder$ClientV2.authenticate(

Caused by: peer not authenticated
at org.apache.http.conn.ssl.AbstractVerifier.verify(
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(
at org.apache.http.impl.client.DefaultRequestDirector.execute(
at org.apache.http.impl.client.AbstractHttpClient.execute(
at org.apache.http.impl.client.AbstractHttpClient.execute(
at org.jboss.resteasy.client.core.executors.ApacheHttpClient4Executor.execute(
at org.jboss.resteasy.client.ClientRequest.execute(
at org.jboss.resteasy.client.ClientRequest.httpMethod(
at org.jboss.resteasy.client.ClientRequest.httpMethod(
at org.openstack4j.connectors.resteasy.HttpCommand.execute(
at org.openstack4j.connectors.resteasy.HttpExecutorServiceImpl.invokeRequest(
at org.openstack4j.connectors.resteasy.HttpExecutorServiceImpl.invoke(

PS: OpenStack4J is awesome, thanks for the good job.


We have encountered the same error.


@olivier-schmitt Hi, I have the same problem just like you when i use version 3.0.2. do you have solve the problem?can you give me some advise. Thanks


Hi, i use version 3.0.0 without bugs for now.


@olivier-schmitt Hi, this might be related to this Config caching issue - #913

You can find out by modifying other parameters in the config such as the max connections (choose something arbitrary like: config.withMaxConnections(7370)


I does not have any effect on my problem.

auhlig commented Jan 5, 2017 edited

Sorry for missing the issue. Not sure what relevant parts changed from 3.0.0 to 3.0.2.
Worht trying a different connector. @olivier-schmitt
Maybe it's only related to resteasy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment