<br><br>Hi,<br><br>I tried similar way , but no luck ... login failed <br><br>server : IP address<br>login : system:root<br>since I am using swauth - I used path as /auth/v1.0 ( even I tried path - "/auth" also ) <br>
<br>You can check the attached scrennshots which shows the swift login using cyberduck<br><br>swift logs : /var/log/syslog <br><br>Apr
27 09:29:04 test3 proxy-server 192.168.x.x 192.168.x.x
27/Apr/2011/03/59/04 GET /v1.0 HTTP/1.0 412 -
Cyberduck/4.0.2%20%288601%29%<div id=":vp">20%28Windows%20XP/5.1%29%20%28x86%29 - - - - txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005<br>
Apr 27 09:29:13 test3 proxy-server 192.168.x.x 192.168.x.x
27/Apr/2011/03/59/13 GET /v1.0 HTTP/1.0 412 -
Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx781d965e-edea-4853-992f-a84afdf1aefb - 0.0005<br>
Apr 27 09:29:53 test3 proxy-server 192.168.x.x 192.168.x.x
27/Apr/2011/03/59/53 GET /v1.0 HTTP/1.0 412 -
Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx709aa787-0391-40a2-928f-9f16f642f5ee - 0.0005<br>
Apr 27 09:32:42 test3 proxy-server 192.168.x.x 192.168.x.x
27/Apr/2011/04/02/42 GET /v1.0 HTTP/1.0 412 -
Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx28acc218-2c08-40e3-be5e-610b79607c64 - 0.0006<br>
Apr 27 09:34:16 test3 proxy-server 192.168.x.x 192.168.x.x
27/Apr/2011/04/04/16 GET /v1.0 HTTP/1.0 412 -
Cyberduck/4.0.2%20%288601%29%20%28Windows%20XP/5.1%29%20%28x86%29 - - - - tx8e389e6c-a99a-4345-98be-99ad3c79e129 - 0.0005<br>
<br><br>There were no logs w.r.t cyberduck , how to enable the logs in cyberduck( debug mode ) ?<br><br>There were no error messages except the login failed ,,, <br><br>Kindly help to resolve this <br><br><br>Thanks & Regards,<br>
shashi </div><br><br><div class="gmail_quote">On Wed, Apr 27, 2011 at 12:32 AM, <span dir="ltr"><<a href="mailto:openstack-operators-request@lists.openstack.org">openstack-operators-request@lists.openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Send Openstack-operators mailing list submissions to<br>
<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openstack-operators-request@lists.openstack.org">openstack-operators-request@lists.openstack.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openstack-operators-owner@lists.openstack.org">openstack-operators-owner@lists.openstack.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Openstack-operators digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: cyberduck interface to swift ?? (Justin J. Russell)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 26 Apr 2011 09:02:12 -0700<br>
From: "Justin J. Russell" <<a href="mailto:jrussell@thesba.com">jrussell@thesba.com</a>><br>
To: shashidhar v <<a href="mailto:shashidhar.velagandula@gmail.com">shashidhar.velagandula@gmail.com</a>>,<br>
"<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>>, Greg Holt<br>
<<a href="mailto:gholt@rackspace.com">gholt@rackspace.com</a>><br>
Subject: Re: [Openstack-operators] cyberduck interface to swift ??<br>
Message-ID:<br>
<401C063992AB5C47B4AF4D8F2FC6C3090175A3F392FE@NTSEXCHA1CMB2.NTS.PHX1><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
I was able to connect to our own implementation of Swift using the following settings:<br>
<br>
Server: <a href="http://storage.webcontrolcenter.com" target="_blank">storage.webcontrolcenter.com</a><br>
Port: 11000<br>
Username: AccountName:UserName<br>
Path: /auth<br>
<br>
The username is your account name + ":" + your username. For example, if your account name is "Account1" and your username is "User1" then your username in Cyberduck is Account1:User1.<br>
<br>
I hope this helps.<br>
<br>
Thank you,<br>
<br>
Justin J. Russell | Vice President of Product Development of Technology Services<br>
<br>
[cid:image001.png@01CC03F0.9FF6AE80]<<a href="http://www.thesba.com/" target="_blank">http://www.thesba.com/</a>><br>
<br>
From: <a href="mailto:openstack-operators-bounces@lists.openstack.org">openstack-operators-bounces@lists.openstack.org</a> [mailto:<a href="mailto:openstack-operators-bounces@lists.openstack.org">openstack-operators-bounces@lists.openstack.org</a>] On Behalf Of shashidhar v<br>
Sent: Tuesday, April 26, 2011 6:22 AM<br>
To: <a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>; Greg Holt<br>
Subject: [Openstack-operators] cyberduck interface to swift ??<br>
<br>
Hi,<br>
<br>
I have deployed swift-1.4 dev(SAIO) service running on a test node , able to create the accounts and do upload/download of files using the "st" tool by following doc of SAIO<br>
Test node swift service is enabled with SSL using self signed certs. and uses swauth authentication<br>
<br>
And, then I have installed the Cyberduck-Installer-4.0.2.exe on windows xp and windows vista machines , but when I open connection to swift service running on test node it throws error as login failed<br>
<br>
swift@test3:~$ swift@test3:~$ st -A <a href="https://192.168.62.63:8080/auth/v1.0" target="_blank">https://192.168.62.63:8080/auth/v1.0</a> -U system:root -K testpass stat<br>
Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f<br>
Containers: 0<br>
Objects: 0<br>
Bytes: 0<br>
Accept-Ranges: bytes<br>
swift@test3:~$<br>
swift@test3:~$<br>
swift@test3:~$ st -A <a href="https://192.168.62.63:8080/auth/v1.0" target="_blank">https://192.168.62.63:8080/auth/v1.0</a> -U system:root -K testpass list<br>
swift@test3:~$<br>
swift@test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H 'X-Storage-Pass: testpass' <a href="https://192.168.62.63:8080/auth/v1.0" target="_blank">https://192.168.62.63:8080/auth/v1.0</a><br>
* About to connect() to 192.168.62.63 port 8080 (#0)<br>
* Trying 192.168.62.63... connected<br>
* Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0)<br>
* successfully set certificate verify locations:<br>
* CAfile: none<br>
CApath: /etc/ssl/certs<br>
* SSLv3, TLS handshake, Client hello (1):<br>
* SSLv3, TLS handshake, Server hello (2):<br>
* SSLv3, TLS handshake, CERT (11):<br>
* SSLv3, TLS handshake, Server finished (14):<br>
* SSLv3, TLS handshake, Client key exchange (16):<br>
* SSLv3, TLS change cipher, Client hello (1):<br>
* SSLv3, TLS handshake, Finished (20):<br>
* SSLv3, TLS change cipher, Client hello (1):<br>
* SSLv3, TLS handshake, Finished (20):<br>
* SSL connection using AES256-SHA<br>
* Server certificate:<br>
* subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=<a href="mailto:shashidharv@ctsf.cdac.org.in">shashidharv@ctsf.cdac.org.in</a><mailto:<a href="mailto:shashidharv@ctsf.cdac.org.in">shashidharv@ctsf.cdac.org.in</a>><br>
* start date: 2011-04-25 05:45:12 GMT<br>
* expire date: 2011-05-25 05:45:12 GMT<br>
* common name: swift (does not match '192.168.62.63')<br>
* issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF; CN=swift; emailAddress=<a href="mailto:shashidharv@ctsf.cdac.org.in">shashidharv@ctsf.cdac.org.in</a><mailto:<a href="mailto:shashidharv@ctsf.cdac.org.in">shashidharv@ctsf.cdac.org.in</a>><br>
* SSL certificate verify result: self signed certificate (18), continuing anyway.<br>
> GET /auth/v1.0 HTTP/1.1<br>
> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k zlib/<a href="http://1.2.3.3" target="_blank">1.2.3.3</a><<a href="http://1.2.3.3" target="_blank">http://1.2.3.3</a>> libidn/1.15<br>
> Host: <a href="http://192.168.62.63:8080" target="_blank">192.168.62.63:8080</a><<a href="http://192.168.62.63:8080" target="_blank">http://192.168.62.63:8080</a>><br>
> Accept: */*<br>
> X-Storage-User: system:root<br>
> X-Storage-Pass: testpass<br>
><br>
< HTTP/1.1 200 OK<br>
< X-Storage-Url: <a href="https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f" target="_blank">https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f</a><br>
< X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22<br>
< X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22<br>
< Content-Length: 117<br>
< Date: Tue, 26 Apr 2011 12:48:39 GMT<br>
<<br>
* Connection #0 to host 192.168.62.63 left intact<br>
* Closing connection #0<br>
* SSLv3, TLS alert, Client hello (1):<br>
{"storage": {"default": "local", "local": "<a href="https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f" target="_blank">https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f</a>"}}swift@test3:~$<br>
swift@test3:~$<br>
<br>
<br>
Using st tool I am able upload/download the files but using cyberduck interface , login itself is failed<br>
<br>
Kindly help me to resolve this login error , any doc. which describes about cyberduck interface to swift will be helpful <<a href="http://cyberduck.ch/windows/Cyberduck-Installer-4.0.2.exe" target="_blank">http://cyberduck.ch/windows/Cyberduck-Installer-4.0.2.exe</a>><br>
I have checked the related doc. present under <a href="http://swift.openstack.org/howto_cyberduck.html" target="_blank">http://swift.openstack.org/howto_cyberduck.html</a> but it describes about source build of cyberduck not the binary version<br>
<br>
Is it possible to specify "http" protocol instead of "https" using cyerduck to contact swift service ?<br>
kindly help me<br>
<br>
Thanks & Regards,<br>
shashi<br>
<br>
________________________________<br>
Notice: This communication, including attachments, may contain information that is confidential. It constitutes non-public information intended to be conveyed only to the designated recipient(s). If the reader or recipient of this communication is not the intended recipient, an employee or agent of the intended recipient who is responsible for delivering it to the intended recipient, or if you believe that you have received this communication in error, please notify the sender immediately by return e-mail and promptly delete this e-mail, including attachments without reading or saving them in any manner. The unauthorized use, dissemination, distribution, or reproduction of this e-mail, including attachments, is prohibited and may be unlawful. If you have received this email in error, please notify us immediately by e-mail or telephone and delete the e-mail and the attachments (if any).<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.html" target="_blank">http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: image001.png<br>
Type: image/png<br>
Size: 13536 bytes<br>
Desc: image001.png<br>
URL: <<a href="http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.png" target="_blank">http://lists.openstack.org/pipermail/openstack-operators/attachments/20110426/0d9d7598/attachment.png</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Openstack-operators mailing list<br>
<a href="mailto:Openstack-operators@lists.openstack.org">Openstack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
<br>
End of Openstack-operators Digest, Vol 6, Issue 10<br>
**************************************************<br>
</blockquote></div><br>