You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "James E. Blair (Created) (JIRA)" <ji...@apache.org> on 2012/03/22 00:24:22 UTC

[dev] [jira] [Created] (LIBCLOUD-172) OpenStack tenantName should be able to be provided when authenticating

OpenStack tenantName should be able to be provided when authenticating
----------------------------------------------------------------------

                 Key: LIBCLOUD-172
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-172
             Project: Libcloud
          Issue Type: Bug
            Reporter: James E. Blair
         Attachments: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch

Providing a tenantName parameter when authenticating will return
a token scoped to that tenant.  Some OpenStack providers will return
a token scoped to the default tenant if it is omitted.  Others require
the tenantName parameter on authentication in order to return useful
endpoints.  This change adds the ex_tenant_name parameter to the
OpenStack NodeDriver and passes it to the identity service if it's
present.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Updated] (LIBCLOUD-172) OpenStack tenantName should be able to be provided when authenticating

Posted by "Tomaz Muraus (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Muraus updated LIBCLOUD-172:
----------------------------------

    Fix Version/s: 0.9.1
    
> OpenStack tenantName should be able to be provided when authenticating
> ----------------------------------------------------------------------
>
>                 Key: LIBCLOUD-172
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-172
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: James E. Blair
>             Fix For: 0.9.1
>
>         Attachments: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch
>
>
> Providing a tenantName parameter when authenticating will return
> a token scoped to that tenant.  Some OpenStack providers will return
> a token scoped to the default tenant if it is omitted.  Others require
> the tenantName parameter on authentication in order to return useful
> endpoints.  This change adds the ex_tenant_name parameter to the
> OpenStack NodeDriver and passes it to the identity service if it's
> present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Resolved] (LIBCLOUD-172) OpenStack tenantName should be able to be provided when authenticating

Posted by "Tomaz Muraus (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Muraus resolved LIBCLOUD-172.
-----------------------------------

    Resolution: Fixed

Merged, thanks.
                
> OpenStack tenantName should be able to be provided when authenticating
> ----------------------------------------------------------------------
>
>                 Key: LIBCLOUD-172
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-172
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: James E. Blair
>         Attachments: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch
>
>
> Providing a tenantName parameter when authenticating will return
> a token scoped to that tenant.  Some OpenStack providers will return
> a token scoped to the default tenant if it is omitted.  Others require
> the tenantName parameter on authentication in order to return useful
> endpoints.  This change adds the ex_tenant_name parameter to the
> OpenStack NodeDriver and passes it to the identity service if it's
> present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Commented] (LIBCLOUD-172) OpenStack tenantName should be able to be provided when authenticating

Posted by "James E. Blair (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LIBCLOUD-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235208#comment-13235208 ] 

James E. Blair commented on LIBCLOUD-172:
-----------------------------------------

API reference:

http://docs.openstack.org/api/openstack-identity-service/2.0/content/POST_authenticate_v2.0_tokens_Service_API_Client_Operations.html

It refers to tenantId, but tenantName seems to be used in practice.  I've filed a doc bug in OpenStack to clear that up.

                
> OpenStack tenantName should be able to be provided when authenticating
> ----------------------------------------------------------------------
>
>                 Key: LIBCLOUD-172
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-172
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: James E. Blair
>         Attachments: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch
>
>
> Providing a tenantName parameter when authenticating will return
> a token scoped to that tenant.  Some OpenStack providers will return
> a token scoped to the default tenant if it is omitted.  Others require
> the tenantName parameter on authentication in order to return useful
> endpoints.  This change adds the ex_tenant_name parameter to the
> OpenStack NodeDriver and passes it to the identity service if it's
> present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Updated] (LIBCLOUD-172) OpenStack tenantName should be able to be provided when authenticating

Posted by "James E. Blair (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. Blair updated LIBCLOUD-172:
------------------------------------

    Attachment: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch
    
> OpenStack tenantName should be able to be provided when authenticating
> ----------------------------------------------------------------------
>
>                 Key: LIBCLOUD-172
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-172
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: James E. Blair
>         Attachments: f1c7907d6c089aa3cb952182ae6c1579caeed383.patch
>
>
> Providing a tenantName parameter when authenticating will return
> a token scoped to that tenant.  Some OpenStack providers will return
> a token scoped to the default tenant if it is omitted.  Others require
> the tenantName parameter on authentication in order to return useful
> endpoints.  This change adds the ex_tenant_name parameter to the
> OpenStack NodeDriver and passes it to the identity service if it's
> present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira