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

Profiles using AWS Signature Version 4 can cause AuthenticationHeaderSignatureVersion exceptions #10217

cyberduck opened this issue Feb 7, 2018 · 1 comment
bug fixed s3 AWS S3 Protocol Implementation


Copy link

cyberduck commented Feb 7, 2018

57cbee5 created the issue

Latest snapshot build of Cyberduck supports OCI Object Storage since ticket #10194.

It works however when downloading files from Object Storage to local folder, it gives the following error after the download is completed.

Unknown application error. No enum constant ch.cyberduck.core.s3.S3Protocol.AuthenticationHeaderSignatureVersion.AWS4.

Download succeeds and the file is copied to local destination if you simply cancel it. If you retry it, Transfer windows turns to red stating it is 0 bytes and "Incomplete" (downloaded file stays, uncorrupted).

I am using this profile.

Setting the Authorization key in configuration to AWS4-HMAC-SHA256 results in a similar error:

Unknown application error. No enum constant ch.cyberduck.core.s3.S3Protocol.AuthenticationHeaderSignatureVersion.AWS4-HMAC-SHA256.

Looking through the code and making some educated guesses, setting the Authorization key to AWS4HMACSHA256 works.

This is a little unintuitive and I couldn't find a reference in cyberduckprofile documentation.

So is this configuration with AWS4HMACSHA256 key correct and how it is supposed to be? If so, documenting it might be useful.

Copy link
Collaborator Author

cyberduck commented Feb 9, 2018

@dkocher commented

I have updated the documentation. Fix in 393d576.

@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.
bug fixed s3 AWS S3 Protocol Implementation
None yet

No branches or pull requests

2 participants