jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-523) Add support for Swift Api Auth
Date Fri, 28 Nov 2014 23:44:12 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228553#comment-14228553

ASF subversion and git services commented on JCLOUDS-523:

Commit 8912650e8405380349dd653e50da06bb75fd156f in jclouds's branch refs/heads/1.8.x from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=8912650 ]

JCLOUDS-523 fix typo in implementation.

> Add support for Swift Api Auth
> ------------------------------
>                 Key: JCLOUDS-523
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-523
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-core
>            Reporter: Fabian Lange
>            Assignee: Adrian Cole
>              Labels: swift
>             Fix For: 1.8.2, 1.9.0
> I was using the deprecated SwiftClient and authentication against it by using the "swift"
provider and "/auth" endpoint.
> I was convinced I should use the new SwiftApi from labs to give feedback. However I cannot,
because the labs requires keystone auth, which we have not set up. We authenticate directly
against radosgw. Because this was possible in 1.7.1 SwiftClient, I consider this missing functionality
in the SwiftApi labs.

This message was sent by Atlassian JIRA

View raw message