Cyberduck Mountain Duck CLI

Opened 7 years ago

Closed 5 years ago

Last modified 5 years ago

#6521 closed enhancement (fixed)

Update client library

Reported by: Juhieta Owned by: dkocher
Priority: normal Milestone: 4.5
Component: azure Version: 4.2.1
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description (last modified by dkocher)

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.

Change History (25)

comment:1 Changed 7 years ago by Juhieta

  • Description modified (diff)

comment:2 Changed 7 years ago by dkocher

  • Description modified (diff)
  • Milestone set to 4.3

comment:3 Changed 7 years ago by dkocher

The other issue refers to #6468.

comment:4 Changed 7 years ago by dkocher

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.

comment:5 follow-up: Changed 7 years ago by Juhieta

Ok, hopefully this can be fixed soon!

comment:6 in reply to: ↑ 5 ; follow-up: Changed 7 years ago by dkocher

Replying to Juhieta:

Ok, hopefully this can be fixed soon!

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

comment:7 in reply to: ↑ 6 ; follow-up: Changed 7 years ago by Juhieta

Replying to dkocher:

Replying to 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?

comment:8 in reply to: ↑ 7 ; follow-up: Changed 7 years ago by dkocher

Replying to Juhieta:

Replying to dkocher:

Replying to 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.

comment:9 in reply to: ↑ 8 ; follow-up: Changed 7 years ago by Juhieta

Replying to dkocher:

Replying to Juhieta:

Replying to dkocher:

Replying to 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.

Last edited 7 years ago by Juhieta (previous) (diff)

comment:10 in reply to: ↑ 9 Changed 7 years ago by dkocher

Replying to 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.

comment:11 Changed 7 years ago by dkocher

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

comment:12 Changed 7 years ago by Juhieta

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

comment:13 Changed 7 years ago by dkocher

#6581 closed as duplicate.

comment:14 follow-up: Changed 6 years ago by Alexey Palazhchenko

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

comment:15 in reply to: ↑ 14 Changed 6 years ago by stevenrobert

Replying to 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.

comment:16 Changed 6 years ago by g1ngernut

+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.)

comment:17 Changed 6 years ago by dkocher

  • Milestone 4.4 deleted
  • Owner changed from yla to dkocher
  • Priority changed from highest to normal
  • Status changed from new to assigned
  • Type changed from defect to enhancement

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

comment:18 Changed 6 years ago by dkocher

  • Summary changed from Unable to connect to Windows Azure Storage to Update client library

comment:19 Changed 5 years ago by dkocher

Azure protocol support is currently not available.

comment:20 Changed 5 years ago by b e

If you want Azure support brought back to Cyberduck, leave your opinion here.

I definitely want Azure support back.

Last edited 5 years ago by dkocher (previous) (diff)

comment:21 Changed 5 years ago by dkocher

  • Milestone set to 4.5

comment:22 Changed 5 years ago by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r14248.

comment:23 Changed 5 years ago by dkocher

Enable support in current snapshot builds with setting the hidden property connection.protocol.azure.enable to true

defaults write ch.sudo.cyberduck connection.protocol.azure.enable true

Last edited 5 years ago by dkocher (previous) (diff)

comment:24 Changed 5 years ago by dkocher

Download the Azure connection profile to enable Windows Azure Storage support in the current snapshot builds.

comment:25 Changed 5 years ago by dkocher

Enabled by default in r14518.

Note: See TracTickets for help on using tickets.
swiss made software