You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Dave King (Created) (JIRA)" <ji...@apache.org> on 2012/03/09 16:28:57 UTC
[dev] [jira] [Created] (LIBCLOUD-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
OpenStack BaseConnection: Allow Passing in an Auth Token
--------------------------------------------------------
Key: LIBCLOUD-164
URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
Project: Libcloud
Issue Type: New Feature
Components: Core
Reporter: Dave King
Priority: Minor
Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Tomaz Muraus (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus updated LIBCLOUD-164:
----------------------------------
Fix Version/s: 0.9.1
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Fix For: 0.9.1
>
> Attachments: libcloud-164-attempt-2.patch, libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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] [Closed] (LIBCLOUD-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus closed LIBCLOUD-164.
---------------------------------
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Fix For: 0.9.1
>
> Attachments: libcloud-164-attempt-2.patch, libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-164:
-------------------------------
Attachment: libcloud-164-attempt-2.patch
The previous patch, but throws an exception when auth_token is provided and base_url is not.
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-164-attempt-2.patch, libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Tomaz Muraus (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomaz Muraus resolved LIBCLOUD-164.
-----------------------------------
Resolution: Fixed
Merged, thanks.
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-164-attempt-2.patch, libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Dave King (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave King updated LIBCLOUD-164:
-------------------------------
Attachment: libcloud-164.patch
First attempt at a patch.
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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-164) OpenStack BaseConnection: Allow
Passing in an Auth Token
Posted by "Dave King (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LIBCLOUD-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228721#comment-13228721 ]
Dave King commented on LIBCLOUD-164:
------------------------------------
(05:17:07 PM) Kami_: tildedave: I guess it would also make sense to update OpenStack 1.0 and 1.1 NodeDriver so they also pass ex_force_auth_token to the parent class
> OpenStack BaseConnection: Allow Passing in an Auth Token
> --------------------------------------------------------
>
> Key: LIBCLOUD-164
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-164
> Project: Libcloud
> Issue Type: New Feature
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-164-attempt-2.patch, libcloud-164.patch
>
>
> Currently if you use Libcloud naively inside a web application, it will re-auth on each individual request that as user makes through the browser.
> It would be beneficial to allow OpenStack connection classes to be instantiated with an argument that allows them to use an existing authentication token.
> Because the authentication process determines the base URL (by extracting the service catalog and individual service tenantIDs), specifying the authentication token (and so skipping authentication) on creating the driver should also require specifying the base URL.
--
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