[
https://issues.apache.org/jira/browse/LIBCLOUD-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089317#comment-14089317
]
Tomaz Muraus edited comment on LIBCLOUD-603 at 8/7/14 3:06 PM:
---------------------------------------------------------------
I pushed initial (and very hacky) support for authenticating against Keystone
API v3 to trunk today -
https://github.com/apache/libcloud/commit/ebb8f098caf8087e6255856f4bd86fe6e9c70e42
:
Known issues / limitations:
1. Domains are not supported yet
2. Projects are supported by specifying "ex_tenant_name" argument
3. Code is currently hacky and fragile (I will improve and refactor it and add
tests over the upcoming weekend)
4. I've only tested it against OpenStack Icehouse release
The code I've used to authenticate using Keystone API v3 is available here -
https://gist.github.com/Kami/3380c7ee00d5614b1f7a
was (Author: kami):
I pushed initial (and very hacky) support for authenticating against Keystone
API v3 to trunk today -
https://github.com/apache/libcloud/commit/ebb8f098caf8087e6255856f4bd86fe6e9c70e42:
Known issues / limitations:
1. Domains are not supported yet
2. Projects are supported by specifying "ex_tenant_name" argument
3. Code is currently hacky and fragile (I will improve and refactor it and add
tests over the upcoming weekend)
4. I've only tested it against OpenStack Icehouse release
The code I've used to authenticate using Keystone API v3 is available here -
https://gist.github.com/Kami/3380c7ee00d5614b1f7a
> Openstack Identity/Keystone v3 API not supported
> ------------------------------------------------
>
> Key: LIBCLOUD-603
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-603
> Project: Libcloud
> Issue Type: Improvement
> Reporter: Dag Stenstad
>
> With the Identity v2.0 API marked as deprecated in Icehouse (alltho reverted
> after release), cloud providers are starting to require using the v3 API to
> authenticate.
> This is needed to support domains, to achieve full multi-tenancy in public
> clouds.
> The v2.0 API seems to be scheduled for removal in the Kilo release next year.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
