[
https://issues.apache.org/jira/browse/JCLOUDS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226411#comment-14226411
]
Jeremy Daggett commented on JCLOUDS-523:
----------------------------------------
Adrian, it should be called TempAuth as referred to in the docs. Please use
that name, as its common nomenclature.
There are actually several
[formats|https://github.com/openstack/swift/blob/698919e67b24a5e0c96dd0c99ee7b8b8f6d728ec/swift/common/middleware/tempauth.py#L522]
that Swift supports with TempAuth.
> 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
(v6.3.4#6332)
