Open Stack

Hi,

I tried similar way , but no luck ... login failed

since I am using swauth -  I used path as /auth/v1.0    ( even I tried  path
- "/auth" also )

You can check the attached scrennshots  which shows the swift login using
cyberduck

swift logs  : /var/log/syslog

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%20%28Windows%20XP/5.1%29%20%28x86%29 - - - -
txd48e8456-2803-4235-9fb1-1c2b443e33b3 - 0.0005
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
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
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
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


There were no logs w.r.t cyberduck ,  how to enable the logs in cyberduck(
debug mode )  ?

There were no error messages except the login failed ,,,

Kindly help to resolve this


Thanks & Regards,
shashi





On Tue, Apr 26, 2011 at 9:32 PM, Justin J. Russell <jrussell at thesba.com>wrote:

>  I was able to connect to our own implementation of Swift using the
> following settings:
>
>
>
> Server: storage.webcontrolcenter.com
>
> Port: 11000
>
> Username: AccountName:UserName
>
> Path: /auth
>
>
>
> 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.
>
>
>
> I hope this helps.
>
>
>
> Thank you,
>
>
>
> Justin J. Russell *|* Vice President of Product Development of Technology
> Services
>
>
>
> [image: Description: Description: Description: thesbalogo]<http://www.thesba.com/>
>
>
>
> *From:* openstack-operators-bounces at lists.openstack.org [mailto:
> openstack-operators-bounces at lists.openstack.org] *On Behalf Of *shashidhar
> v
> *Sent:* Tuesday, April 26, 2011 6:22 AM
> *To:* openstack-operators at lists.openstack.org; Greg Holt
> *Subject:* [Openstack-operators] cyberduck interface to swift ??
>
>
>
> Hi,
>
> 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
>  Test node swift service is enabled with SSL using self signed certs. and
> uses swauth authentication
>
> 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
>
> swift at test3:~$ swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0-U system:root -K testpass stat
>    Account: AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f
> Containers: 0
>    Objects: 0
>      Bytes: 0
> Accept-Ranges: bytes
> swift at test3:~$
> swift at test3:~$
> swift at test3:~$ st -A https://192.168.62.63:8080/auth/v1.0 -U system:root
> -K testpass list
> swift at test3:~$
> swift at test3:~$ curl -k -v -H 'X-Storage-User: system:root' -H
> 'X-Storage-Pass: testpass' https://192.168.62.63:8080/auth/v1.0
> * About to connect() to 192.168.62.63 port 8080 (#0)
> *   Trying 192.168.62.63... connected
> * Connected to 192.168.62.63 (192.168.62.63) port 8080 (#0)
> * successfully set certificate verify locations:
> *   CAfile: none
>   CApath: /etc/ssl/certs
> * SSLv3, TLS handshake, Client hello (1):
> * SSLv3, TLS handshake, Server hello (2):
> * SSLv3, TLS handshake, CERT (11):
> * SSLv3, TLS handshake, Server finished (14):
> * SSLv3, TLS handshake, Client key exchange (16):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSLv3, TLS change cipher, Client hello (1):
> * SSLv3, TLS handshake, Finished (20):
> * SSL connection using AES256-SHA
> * Server certificate:
> *        subject: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF;
> CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in
> *        start date: 2011-04-25 05:45:12 GMT
> *        expire date: 2011-05-25 05:45:12 GMT
> *        common name: swift (does not match '192.168.62.63')
> *        issuer: C=IN; ST=KARNATAKA; L=BANGALORE; O=CDAC; OU=CTSF;
> CN=swift; emailAddress=shashidharv at ctsf.cdac.org.in
> *        SSL certificate verify result: self signed certificate (18),
> continuing anyway.
> > GET /auth/v1.0 HTTP/1.1
> > User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7 OpenSSL/0.9.8k
> zlib/1.2.3.3 libidn/1.15
> > Host: 192.168.62.63:8080
> > Accept: */*
> > X-Storage-User: system:root
> > X-Storage-Pass: testpass
> >
> < HTTP/1.1 200 OK
> < X-Storage-Url:
> https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f
> < X-Storage-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22
> < X-Auth-Token: AUTH_tka5f5ea0695bd4cadb5a4b624c5418f22
> < Content-Length: 117
> < Date: Tue, 26 Apr 2011 12:48:39 GMT
> <
> * Connection #0 to host 192.168.62.63 left intact
> * Closing connection #0
> * SSLv3, TLS alert, Client hello (1):
> {"storage": {"default": "local", "local": "
> https://192.168.62.63:8080/v1/AUTH_4b3f583b-a3e9-4abe-8aef-44d333ab8b3f
> "}}swift at test3:~$
> swift at test3:~$
>
>
> Using st tool I am able upload/download the files but using cyberduck
> interface , login itself is failed
>
> Kindly help me to resolve this login error ,  any doc. which  describes
> about cyberduck interface to swift will be helpful
> <http://cyberduck.ch/windows/Cyberduck-Installer-4.0.2.exe>
> I have checked the related doc. present under
> http://swift.openstack.org/howto_cyberduck.html  but it describes about
> source build of cyberduck not the binary version
>
> Is it possible to specify "http" protocol  instead of "https" using
> cyerduck to contact swift service ?
> kindly help me
>
> Thanks & Regards,
> shashi
>
> ------------------------------
> 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).
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20110427/f53ebd33/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swift1.JPG
Type: image/jpeg
Size: 133530 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20110427/f53ebd33/attachment-0006.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swift2.JPG
Type: image/jpeg
Size: 118924 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20110427/f53ebd33/attachment-0007.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: swift3.JPG
Type: image/jpeg
Size: 118924 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20110427/f53ebd33/attachment-0008.jpe>