Re: Connect to hubiC

[Ignasi Barrera]

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 should be implemented in the OAuth API, and so should be the
refresh token features, as tokens emitted by hubiC seem to expire.


I.


On 9 March 2016 at 18:02, GARDAIS Ionel  wrote:
> 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 the storage or 
> should a dedicated provider be developped ?
>
> Thanks for your help,
> Ionel
> --
> Beicip-Franlab SA - 232 av. Napoléon Bonaparte - BP 2132-92502 
> Rueil-Malmaison Cedex
> Capital: EUR 6 000 000 - TVA FR 54 679 804 047- RCS Nanterre 679 804 047
> This message and any attachments (the message) are confidential and intended 
> solely for the addressees.
> Any unauthorised use, dissemination or reproduction is strictly prohibited.
> The sender does not accept liability for any errors or omissions in the 
> contents of this message arising as a result of e-mail transmission.

Connect to hubiC

[GARDAIS Ionel]

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 the storage or should 
a dedicated provider be developped ?

Thanks for your help,
Ionel
--
Beicip-Franlab SA - 232 av. Napoléon Bonaparte - BP 2132-92502 Rueil-Malmaison 
Cedex
Capital: EUR 6 000 000 - TVA FR 54 679 804 047- RCS Nanterre 679 804 047
This message and any attachments (the message) are confidential and intended 
solely for the addressees.
Any unauthorised use, dissemination or reproduction is strictly prohibited.
The sender does not accept liability for any errors or omissions in the 
contents of this message arising as a result of e-mail transmission.