Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AWS Signature V4 Default Breaks EMC ECS Connectivity #9694

Closed
cyberduck opened this issue Sep 14, 2016 · 2 comments
Closed

AWS Signature V4 Default Breaks EMC ECS Connectivity #9694

cyberduck opened this issue Sep 14, 2016 · 2 comments
Labels
bug duplicate high priority s3 AWS S3 Protocol Implementation
Milestone
5.1.3

Comments

@cyberduck
Copy link
Collaborator

37e1d8c created the issue

Hello, I downloaded the latest version of Cyberduck but had to fall back to v 5.0.11 the new feature you added called "[Feature] Default to signature version AWS4 when connecting to third party S3 providers" is breaking S3 authentication to EMC's 3rd party S3 storage arrays - ECS.

The error returned is shown in the attached screenshot.

Can you please create a UI element that lets me specify the S3 signature version on a per-bookmark basis? I couldn't find out how to switch this in the options so I had to uninstall the new version of the software and go back to using an older version.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #9667. Please update to the latest snapshot build available and use the new AWS2 signature version connection profile .

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug duplicate high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
5.1.3
Development

No branches or pull requests
1 participant
@cyberduck