[
https://issues.apache.org/jira/browse/JCLOUDS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-223:
-----------------------------------
Attachment: JCLOUDS-223.patch
> Authentication token should be cached and reused when authenticating with
> Abiquo
> --------------------------------------------------------------------------------
>
> Key: JCLOUDS-223
> URL: https://issues.apache.org/jira/browse/JCLOUDS-223
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-labs
> Affects Versions: 1.6.1
> Reporter: Ignasi Barrera
> Assignee: Ignasi Barrera
> Labels: abiquo
> Fix For: 1.7.0
>
> Attachments: JCLOUDS-223.patch
>
>
> Currently there are two ways to authenticate against the Abiquo API:
> * Using Basic Authentication.
> * Using an authentication token.
> The first one can be used to perform any request to the Abiquo API, but it is
> not the recommended way to interact with it. Instead, a better way to d that
> is to use basic auth to perform a login request and get an authentication
> token, and then use that token in the subsequent requests to the API.
> Currently jclouds supports authenticating with the token, but the context
> must be created with it and it is not automatically obtained. This should be
> an automatic and transparent process, similar to the OpenStack authentication
> module [1].
> [1]
> https://github.com/jclouds/jclouds/blob/master/common/openstack/src/main/java/org/jclouds/openstack/config/OpenStackAuthenticationModule.java
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
