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

Allow connections to thirdparty S3 using AWS2 signature authentication #9667

Closed
cyberduck opened this issue Aug 25, 2016 · 6 comments
Closed

Allow connections to thirdparty S3 using AWS2 signature authentication #9667

cyberduck opened this issue Aug 25, 2016 · 6 comments
Labels
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 25, 2016

1a69648 created the issue

Upon updating to 5.1.0 all my S3 links are not working.
Transmit works with the same S3 links.
I try creating a new bookmark using all S3 credentials in case they got corrupted but got the same error.

Listing director / failed.
Bad Request. Service Error Message.
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 25, 2016

@dkocher commented

Please post the transcript from the log drawer (⌘-L).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 26, 2016

@dkocher commented

Possibly related from defaulting to AWS4 signature version for authentication in 97fee10. As of 61e1690 you can use a new connection profile that will use AWS2 signature version for authentication.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 29, 2016

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 6, 2016

@dkocher commented

#9679 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 14, 2016

@dkocher commented

#9694 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@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.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant