I was able to login to swift using https, just have to confirm continue when cyberduck prompts about the SSL self signed certificate.<div><br></div><div>I am also curious about having cyberduck to connect to S3 with plain http instead of https.</div>
<div><br></div><div>Shi<br><br><div class="gmail_quote">On Tue, Apr 26, 2011 at 7:22 AM, shashidhar v <span dir="ltr"><<a href="mailto:shashidhar.velagandula@gmail.com">shashidhar.velagandula@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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" target="_blank">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" target="_blank">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> libidn/1.15<br>
> Host: <a href="http://192.168.62.63:8080" target="_blank">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"> </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>_______________________________________________<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></blockquote></div><br><br clear="all"><br>-- <br>Shi Jin, Ph.D.<br><br>
</div>