Update client library

[cyberduck]

Juhieta created the issue

Hi,

I purchased the application from Mac App Store to connect Windows Azure Storage (blob storage).

The Mac App Store version had some problems to connect to Windows Azure, so I installed the latest version from the website (4.2.1).

However, even with this version, when I enter my credentials correctly and try to connect, I get the following error:

##
DNS Error: Connection failed
blob.core.windows.net
##

The problem seems to be that Cyberduck formulates the Azure Storage URL as follows (where MYACCOUNT is my account name):

https://MYACCOUNT@blob.core.windows.net

While it should be:

https://MYACCOUNT.blob.core.windows.net

This completely breaks Azure compatibility of Cyberduck.

[cyberduck]

@dkocher commented

The other issue refers to #6468.

[cyberduck]

@dkocher commented

This is very much a duplicate of #6246 although the default hostname should possibly be changed. I will have to read up on the Azure documentation.

[cyberduck]

Juhieta commented

Ok, hopefully this can be fixed soon!

[cyberduck]

@dkocher commented

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.

[cyberduck]

Juhieta commented

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

[cyberduck]

@dkocher commented

Replying to [comment:7 Juhieta]:

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

This is possible in both the Connection and Bookmark windows.

[cyberduck]

Juhieta commented

Replying to [comment:8 dkocher]:

Replying to [comment:7 Juhieta]:

Replying to [comment:6 dkocher]:

Replying to [comment:5 Juhieta]:

Ok, hopefully this can be fixed soon!

Until then the workaround described (enter the hostname manually) should work for you.
That would be nice, but I can't find a way to change the hostname manually (not found from the other ticket either). Can you describe the steps to change the full url manually?

This is possible in both the Connection and Bookmark windows.

Unfortunately it is not possible (or at least I can't find a way how). I'm only unable to change the "Server" (not the final URL).

The orignal problem was:

If I enter to Server field "blob.core.windows.net" and to Username field my Azure account name, the application formulates the URL as:

ACCOUNTNAME@blob.core.windows.net

While it should be:

ACCOUNTNAME.blob.core.windows.net

If I now enter to Server field "ACCOUNTNAME.blob.core.windows.net" and try to leave Username field empty, the application will not allow to connect until I also give the Username. And that will result to:

ACCOUNTNAME@ACCOUNTNAME.blob.core.windows.net

If you really think it should be possible to fix the result URL, could you please give step by step instructions.

[cyberduck]

@dkocher commented

Replying to [comment:9 Juhieta]:

I will have to check with my own account. But there should still be a access key that you must use as the username in the login credentials.

[cyberduck]

@dkocher commented

We will need to update switch our client library implementation to Windows Azure SDK for Java.

[cyberduck]

Juhieta commented

Ok, great to hear that something can be done to fix this!

[cyberduck]

@dkocher commented

#6581 closed as duplicate.

[cyberduck]

Alexey Palazhchenko commented

Looks like there are no workarounds? Small bugfix release maybe? Please.

[cyberduck]

806c7f0 commented

Replying to [comment:14 Alexey Palazhchenko]:

Looks like there are no workarounds? Small bugfix release maybe? Please.

Same issue here, would really like to use this tool, but connectivity to Azure not working, will likely have to abandon for something else until fix made available.

[cyberduck]

befde16 commented

+1 for this to be fixed please.

The issue means it is impossible to connect to Azure. (I have just downloaded the Windows version of Cyberduck 4.2.1 and very disappointed.)

[cyberduck]

@dkocher commented

We have removed Azure support completly in e55be0b until we reintroduce support using new API.