[
https://issues.apache.org/jira/browse/JCLOUDS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226359#comment-14226359
]
Adrian Cole commented on JCLOUDS-523:
-------------------------------------
As this particular feature is known by many names, I want to make sure I am
getting the right impl down.
You need to use what is known as TempAuth
http://docs.openstack.org/developer/swift/overview_auth.html
That's obtained via a call to an endpoint usually ending in /auth/v1.0
https://www.swiftstack.com/docs/cookbooks/swift_usage/auth.html
http://docs.openstack.org/api/openstack-object-storage/1.0/content/authentication-object-dev-guide.html
The result of that is the following which designate the url and token for all
following requests:
{code}
StorageURL: http://swift.example.com/v1/AUTH_superman
Auth Token: AUTH_tkb5bab9e25a274b4a853fe2587b5dc8f9
{code}
I'm not sure what to call this.. SwiftAuth? 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)
