Re: Using JClouds without TLSv1.0

Great to see it worked in the end! :) On 10 March 2016 at 15:17, Mop Sophia wrote: > Nice ! It works fine ! > > Thank you very much Ignasi ;) > > 2016-03-10 15:10 GMT+01:00 Ignasi Barrera : >> >> OK, then try this. Create a class like this one [1], that

Re: Using JClouds without TLSv1.0

Nice ! It works fine ! Thank you very much Ignasi ;) 2016-03-10 15:10 GMT+01:00 Ignasi Barrera : > OK, then try this. Create a class like this one [1], that implements > the EndpointToSupplierAdminURI, and just returns the public url > instead of the admin one. Then, bind the

Re: Using JClouds without TLSv1.0

OK, then try this. Create a class like this one [1], that implements the EndpointToSupplierAdminURI, and just returns the public url instead of the admin one. Then, bind the EndpointToSupplierAdminURI to your class, and that should work fine. [1]

Re: Using JClouds without TLSv1.0

It seems that I'm not able to put PublicURLOrInternalIfNull.class as a parameter of to() method because PublicURLOrInternalIfNull does not inherit from EndpointToSupplierAdminURI... The method to(Class) in the type LinkedBindingBuilder is not applicable for the arguments (Class) 2016-03-10

Re: Using JClouds without TLSv1.0

(Moving back the thread to the jclouds user list) Looking at the code, it seems that the User, Token and Tenant apis from keystone use the admin endpoint by default. You can try to change the default behavior and let the public endpoint be picked instead of the admin one. Add the following module

Re: Using JClouds without TLSv1.0

Yes there is, but if I'm not wrong the jclouds default is to use the public url and fallback to the internal one. Do you have any special Guice module configuration? El 9/3/2016 5:36 p. m., "Mop Sophia" escribió: > Thanks Ignasi, it's ok when using the proxy properties (it

Re: Using JClouds without TLSv1.0

Don't configure the proxy in the client supplier. Just configure it the "standard jclouds way", by configuring the proxy properties as "overrides" when creating the context: http://jclouds-javadocs.elasticbeanstalk.com/constant-values.html#org.jclouds.Constants.PROPERTY_PROXY_HOST On 9 March 2016

Re: Using JClouds without TLSv1.0

Hi, Thanks for this code Ignasi, but it seems the client configuration is not used, because the client tries a direct connection without proxy :( Here is my code : public static class TLSOkHttpClientSupplier implements OkHttpClientSupplier { @Override public OkHttpClient get() {

Re: Using JClouds without TLSv1.0

Hi! Andrew's link will provide you the context you need. I don't know if there is a proper way of configuring this using the default HTTP driver, but here is a specific example using the OkHttp one: First you will need to create an OkHttpClientSupplier that creates the http client with the

Re: Using JClouds without TLSv1.0

Hi Stéphane Any idea of code to configure my http client with TLSv1.1 or TLSv1.2 instead of TLSv1.0, please ? The following blog post doesn't provide a step-by-step solution, but should hopefully help: https://jclouds.apache.org/blog/2014/10/25/poodle-and-jclouds/ Regards ap