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

SignatureDoesNotMatch error for signed URLs with AWS4 signing methods #9317

Closed
cyberduck opened this issue Feb 29, 2016 · 3 comments
Closed

SignatureDoesNotMatch error for signed URLs with AWS4 signing methods #9317

cyberduck opened this issue Feb 29, 2016 · 3 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
5.0

Comments

@cyberduck
Copy link
Collaborator

5895ae9 created the issue

Hi,

Today I have update cyberduck to 4.8 and now when I use signed URL it always leaves me this error:

**SignatureDoesNotMatch**

-*The request signature we calculated does not match the signature you provided. Check your key and signing method.**

Key and signing method didn't change and It didn't happen with previous versions.

Thanks and best regards.
Mario
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Looks like this only happens when authenticated with AWS4-HMAC-SHA256.

@cyberduck
Copy link
Collaborator Author

5895ae9 commented

This Authentication Protocol is the only supported for Frankfurt region, and this protocol have been woriking correctly since december, 2014 (https://trac.cyberduck.io/ticket/8386) and only stops working with last ciberduck update.

Please let me know if I can help you.

Thanks and regards,
Mario

Replying to [comment:3 dkocher]:

Looks like this only happens when authenticated with AWS4-HMAC-SHA256.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 4ea9710.

@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

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
5.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck