Cyberduck Mountain Duck CLI

Opened 7 years ago

Closed 6 years ago

Last modified 5 years ago

#6330 closed enhancement (fixed)

Keystone authentication

Reported by: crayon_z Owned by: dkocher
Priority: highest Milestone: 4.4
Component: openstack Version: 4.0.2
Severity: critical Keywords:
Cc: Architecture:
Platform:

Description

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

Attachments (5)

cyberduck.jpg (33.8 KB) - added by crayon_z 7 years ago.
login failed pic
cyberduck_update.jpg (33.6 KB) - added by crayon_z 7 years ago.
cyberduck_update_2.png (28.1 KB) - added by crayon_z 7 years ago.
cyberduck.log (14.8 KB) - added by crayon_z 7 years ago.
swift_configuration.png (37.2 KB) - added by crayon_z 7 years ago.

Download all attachments as: .zip

Change History (47)

comment:1 Changed 7 years ago by crayon_z

  • Type changed from defect to enhancement

comment:2 Changed 7 years ago by crayon_z

  • Severity changed from normal to critical

comment:3 Changed 7 years ago by dkocher

  • Component changed from core to openstack
  • Owner set to dkocher

Please update to the latest release version available.

comment:4 Changed 7 years ago by dkocher

  • Summary changed from Connect to Openstack Swift, Authentication with Keystone to Keystone authentication

comment:5 follow-up: Changed 7 years ago by dkocher

Have you actually tried connecting? It should just work.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 7 years ago by crayon_z

Replying to 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?

comment:7 follow-up: Changed 7 years ago by dkocher

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

comment:8 in reply to: ↑ 6 Changed 7 years ago by dkocher

Replying to crayon_z:

Replying to 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.

comment:10 Changed 7 years ago by dkocher

Related to #5735.

Changed 7 years ago by crayon_z

login failed pic

comment:11 in reply to: ↑ 7 Changed 7 years ago by crayon_z

Replying to 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
Last edited 7 years ago by dkocher (previous) (diff)

comment:12 follow-up: Changed 7 years ago by 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.

comment:13 follow-up: Changed 7 years ago by dkocher

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

comment:14 in reply to: ↑ 12 Changed 7 years ago by crayon_z

Replying to 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?

comment:15 in reply to: ↑ 13 ; follow-up: Changed 7 years ago by crayon_z

Replying to 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?

Changed 7 years ago by crayon_z

comment:16 in reply to: ↑ 15 ; follow-up: Changed 7 years ago by dkocher

Replying to crayon_z:

Replying to 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?

comment:17 in reply to: ↑ 16 Changed 7 years ago by crayon_z

Replying to dkocher:

Replying to crayon_z:

Replying to 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.

Changed 7 years ago by crayon_z

comment:18 follow-up: Changed 7 years ago by 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.

comment:19 in reply to: ↑ 18 Changed 7 years ago by crayon_z

Replying to 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.

comment:20 follow-up: Changed 7 years ago by 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.

comment:21 in reply to: ↑ 20 Changed 7 years ago by dkocher

Replying to 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/.

comment:22 Changed 7 years ago by crayon_z

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.

Last edited 7 years ago by crayon_z (previous) (diff)

comment:23 follow-up: Changed 7 years ago by dkocher

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

Changed 7 years ago by crayon_z

comment:24 in reply to: ↑ 23 Changed 7 years ago by crayon_z

Replying to 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.

Changed 7 years ago by crayon_z

comment:25 Changed 7 years ago by dkocher

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

comment:26 follow-ups: Changed 7 years ago by dkocher

  • Milestone set to 4.1.4
  • Resolution set to worksforme
  • Status changed from new to closed

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

comment:27 in reply to: ↑ 26 ; follow-up: Changed 7 years ago by crayon_z

Replying to 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?

comment:28 in reply to: ↑ 26 Changed 7 years ago by crayon_z

Replying to 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.

comment:29 in reply to: ↑ 27 Changed 7 years ago by dkocher

Replying to 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.

comment:30 Changed 7 years ago by dkocher

  • Milestone changed from 4.2 to 4.3
  • Resolution worksforme deleted
  • Status changed from closed to reopened

comment:31 Changed 7 years ago by dkocher

Documentation for HP Cloud connection setup in the wiki.

comment:33 Changed 7 years ago by dkocher

#6658 closed as duplicate.

comment:34 Changed 6 years ago by dkocher

#6623 closed as duplicate.

comment:35 Changed 6 years ago by dkocher

Rackspace Keystone documentation in the Auth Client DeveloperGuide.

comment:36 Changed 6 years ago by dkocher

OpenStack developer documentation for POST tokens.

comment:37 follow-up: Changed 6 years ago by Ning2008Wisc

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

comment:38 in reply to: ↑ 37 Changed 6 years ago by dkocher

Replying to 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.

comment:39 Changed 6 years ago by dkocher

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).

comment:40 Changed 6 years ago by dkocher

#7072 closed as duplicate.

comment:41 Changed 6 years ago by dkocher

  • Milestone changed from 4.4 to 4.3.2
  • Resolution set to fixed
  • Status changed from reopened to closed

In r11080.

comment:42 Changed 5 years ago by dkocher

#7419 closed as duplicate.

Note: See TracTickets for help on using tickets.
swiss made software