Profiles using AWS Signature Version 4 can cause AuthenticationHeaderSignatureVersion exceptions

[ilker]

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.

[dkocher]

I have updated the documentation. Fix in r43868.