Connect to hubiC

HI list, I’d like to interact with OVH’s hubiC storage. It’s based on OpenStack so it’s likely to be usable with jClouds. Unfortunately, they change the authentication process : auth is based on oauth2. What is the best approach to this ? Can I use oauth2 API then OpenStack API to interact with

Re: requested location eu-central-1, which is not in the configured locations

Hi, I would also like to know how to use AWS S3 v4 signature for authentication. Is there way to specify which signature version to use while constructing a BlobStoreContext? Thanks in advance, Ranjith On Tue, Mar 8, 2016 at 3:24 PM, Archana C wrote: > From the

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: Connect to hubiC

Hi Ionel, The current OAuth API in jclouds just supports the Bearer Token and the JWT authentication flows. Having a look at how OAuth works in hubiC, it seems that you won't be able to use the current API to connect to it. In order to be able to authenticate, the regular Authorization Code flow

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() {