Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keystone authentication #6330

Closed
cyberduck opened this issue Oct 27, 2011 · 39 comments
Closed

Keystone authentication #6330

cyberduck opened this issue Oct 27, 2011 · 39 comments
Assignees
@dkocher
Labels
enhancement fixed openstack OpenStack Swift Protocol Implementation
Milestone
4.4

Comments

@cyberduck
Copy link
Collaborator

6477131 created the issue

How to connect to Openstack Swift with Keystone as its authentication?
Does CyberDuck support this now?

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest release version available.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Have you actually tried connecting? It should just work.

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:5 dkocher]:

Have you actually tried connecting? It should just work.

Yes, I've tried but login failed.
Do I have to modify the user.config file?
Should I fill the content of connection creation view as before?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (⌘-L). I have no Swift installation with Keystone here.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 crayon_z]:

Replying to [comment:5 dkocher]:

Have you actually tried connecting? It should just work.

Yes, I've tried but login failed.
Do I have to modify the user.config file?
Should I fill the content of connection creation view as before?

Yes, first reset your changes to user.config only making changes later when necessary.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is the same as in (https://answers.launchpad.net/swift/+question/175051).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Related to #5735.

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:7 dkocher]:

Please post the transcript from the log drawer (⌘-L). I have no Swift installation with Keystone here.

I reinstall the newest version of CyberDuck and reset user.config to its default status.
Then I tried to login several times but no logs found in the log file.
My swift storage port is 8080 and my keystone auth port is 5000.
When I fill the port with 8080, it just show the login failed window, but when I use port 5000 to login, it turns out the login failed window as the attachment picture I've just uploaded.

In swift, I run the following command:

swift -A http://219.228.106.219:5000/v1.0 -U demo -K front2009 stat -v

And get the response as follows:

StorageURL: https://219.228.106.219:8080/v1/AUTH_6
Auth Token: 6cf63437-b61a-438b-8432-2c335fa7e854
   Account: AUTH_6
Containers: 2
   Objects: 9
     Bytes: 332594154
Accept-Ranges: bytes

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Configure your bookmark to connect to 219.228.106.219 on port 5000 with the Swift HTTP profile installed and selected as the protocol in your bookmark. The default Swift (OpenStack Object Storage) only accepts SSL secured connections.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Make sure to update first to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:12 dkocher]:

Configure your bookmark to connect to 219.228.106.219 on port 5000 with the Swift HTTP profile installed and selected as the protocol in your bookmark. The default Swift (OpenStack Object Storage) only accepts SSL secured connections.

I've installed the new profile, but after that I can't modify the server ip and port. How to configure this?

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:13 dkocher]:

Make sure to update first to the latest snapshot build available.

When I change the update option to "snapshot build" and press the update button, it turns out the error as shown in the picture I just attached. How can I solve this problem?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:15 crayon_z]:

Replying to [comment:13 dkocher]:

Make sure to update first to the latest snapshot build available.

When I change the update option to "snapshot build" and press the update button, it turns out the error as shown in the picture I just attached. How can I solve this problem?

Can you access version.cyberduck.ch in your web browser?

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:16 dkocher]:

Replying to [comment:15 crayon_z]:

Replying to [comment:13 dkocher]:

Make sure to update first to the latest snapshot build available.

When I change the update option to "snapshot build" and press the update button, it turns out the error as shown in the picture I just attached. How can I solve this problem?

Can you access version.cyberduck.ch in your web browser?

I can access that page now but it turns out another error as shown in the attachment.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The download of the update fails due to some networking issue between you and our server. Check that there is no issue with a proxy or firewall at your place.

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:18 dkocher]:

The download of the update fails due to some networking issue between you and our server. Check that there is no issue with a proxy or firewall at your place.

But I can check the release and beta version's update successfully, so I guess maybe it's not the networking issue. I have no firewall or proxy limit configured and, by the way, our GFW seems not blocking the site. It's just the snapshot build version doesn't work.

@cyberduck
Copy link
Collaborator Author

6477131 commented

Is there any other way to put the newest patch?
I access http://update.cyberduck.ch/nightly/ and download the newest *gz file but don't know how to use it.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:20 crayon_z]:

Is there any other way to put the newest patch?
I access http://update.cyberduck.ch/nightly/ and download the newest *gz file but don't know how to use it.

You can download the latest snapshot manually from (http://update.cyberduck.ch/windows/nightly/).

@cyberduck
Copy link
Collaborator Author

6477131 commented

I've installed the snapshot build version and the Swift HTTP profile successfully. Also I configure the swift connection as the way mentioned above(port 5000), but still login failed.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (⌘-L).

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:23 dkocher]:

Please post the transcript from the log drawer (⌘-L).

I just uploaded my CyberDuck log, but it didn't generate any log when I login.It's just the log recorded before.
My configuration is as the picture I've attached.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

If the login fails you should see something in the log drawer (Ctrl-L).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can connect successfully here (although with no valid credentials).

GET /v1.0 HTTP/1.1
x-auth-user: demo
x-auth-key: demo
Host: 219.228.106.219:5000
Connection: Keep-Alive
User-Agent: Cyberduck/4.1.4 (Mac OS X/10.6.8) (x86_64)
HTTP/1.1 401 Unauthorized
Content-Type: application/json; charset=UTF-8
Content-Length: 60
Date: Fri, 28 Oct 2011 13:55:48 GMT
Connection: keep-alive

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:26 dkocher]:

I can connect successfully here (although with no valid credentials).

GET /v1.0 HTTP/1.1
x-auth-user: demo
x-auth-key: demo
Host: 219.228.106.219:5000
Connection: Keep-Alive
User-Agent: Cyberduck/4.1.4 (Mac OS X/10.6.8) (x86_64)
HTTP/1.1 401 Unauthorized
Content-Type: application/json; charset=UTF-8
Content-Length: 60
Date: Fri, 28 Oct 2011 13:55:48 GMT
Connection: keep-alive

Glad to hear that. Which version do you use? Have you modified the user.config file?

@cyberduck
Copy link
Collaborator Author

6477131 commented

Replying to [comment:26 dkocher]:

I can connect successfully here (although with no valid credentials).

GET /v1.0 HTTP/1.1
x-auth-user: demo
x-auth-key: demo
Host: 219.228.106.219:5000
Connection: Keep-Alive
User-Agent: Cyberduck/4.1.4 (Mac OS X/10.6.8) (x86_64)
HTTP/1.1 401 Unauthorized
Content-Type: application/json; charset=UTF-8
Content-Length: 60
Date: Fri, 28 Oct 2011 13:55:48 GMT
Connection: keep-alive

Yea, I made it to. dkocher,thank you for your help.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:27 crayon_z]:

Glad to hear that. Which version do you use? Have you modified the user.config file?

There is no change to a hidden configuration option necessary.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Latest documentation at (http://keystone.openstack.org/api_curl_examples.html)

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Documentation for HP Cloud connection setup in the wiki.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Corresponding ticket at (https://github.com/rackspace/java-cloudfiles/issues/30).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#6658 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#6623 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Rackspace Keystone documentation in the Auth Client DeveloperGuide.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

OpenStack developer documentation for POST tokens.

@cyberduck
Copy link
Collaborator Author

Ning2008Wisc commented

Currently, we have a solution for this issue, please look at Zmanda team blog.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:37 Ning2008Wisc]:

Currently, we have a solution for this issue, please look at Zmanda team blog.

The fork is at (https://github.com/zmanda/java-cloudfiles).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We will have to adjust the fork to be backward compatible with Swift services not running Keystone. Also the patch needs to be adjusted to drop the additional JSON library dependency and switch to use the XML protocol (as the rest of the library).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#7072 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In bcfe433.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#7419 closed as duplicate.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
enhancement fixed openstack OpenStack Swift Protocol Implementation
Projects
None yet
Milestone
4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck