<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I was able to connect to our own implementation of Swift using the following settings:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Server: storage.webcontrolcenter.com<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Port: 11000<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Username: AccountName:UserName<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Path: /auth<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I hope this helps.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E">Justin J. Russell
<b>|</b> Vice President of Product Development of Technology Services<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0F243E"><o:p> </o:p></span></p>
<p class="MsoNormal"><a href="http://www.thesba.com/"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;text-decoration:none"><img border="0" width="243" height="73" id="Picture_x0020_1" src="cid:image001.png@01CC03F0.9FF6AE80" alt="Description: Description: Description: thesbalogo"></span></a><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> openstack-operators-bounces@lists.openstack.org [mailto:openstack-operators-bounces@lists.openstack.org]
<b>On Behalf Of </b>shashidhar v<br>
<b>Sent:</b> Tuesday, April 26, 2011 6:22 AM<br>
<b>To:</b> openstack-operators@lists.openstack.org; Greg Holt<br>
<b>Subject:</b> [Openstack-operators] cyberduck interface to swift ??<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">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">
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">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">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><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><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">1.2.3.3</a> libidn/1.15<br>
> Host: <a href="http://192.168.62.63:8080">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">
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">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">
</a><br>
I have checked the related doc. present under <a href="http://swift.openstack.org/howto_cyberduck.html">
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 <o:p></o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Navy" size="1">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>
</font>
</body>
</html>