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

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

Closed
eon8ight opened this Issue Jul 9, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@eon8ight

eon8ight commented Jul 9, 2018

CPAN upgraded to 0.82 over the weekend, even though it seems 0.82 hasn't been released yet. This bug may exist in 0.81. Calling Net::Amazon::S3::Bucket->add_key_filename() silently fails, and the errstr is this:

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

@ranguard

This comment has been minimized.

Collaborator

ranguard commented Jul 9, 2018

Sorry I'm new to releases on Github - forgot to do it. @branislav-zahradnik-gdc ideas on the signature?

@branislav-zahradnik-gdc

This comment has been minimized.

branislav-zahradnik-gdc commented Jul 10, 2018

@eon8ight can you please share:

  • which region is your bucket ?
  • value of key ?

I came around this error as well, can be either unexpected redirect or wrong evaluation of key path.

@eon8ight

This comment has been minimized.

eon8ight commented Jul 10, 2018

@branislav-zahradnik-gdc
The region is us-east-1 and one of the keys used is /tmp/customer/transient/20180710_100517.fb74f6066c4623f970f7a84f9b437fe05b44bd1b302918.20828449.csv.

@branislav-zahradnik-gdc

This comment has been minimized.

branislav-zahradnik-gdc commented Jul 10, 2018

thank you, I'll look into it

branislav-zahradnik-gdc added a commit to branislav-zahradnik-gdc/net-amazon-s3 that referenced this issue Jul 10, 2018

branislav-zahradnik-gdc added a commit to branislav-zahradnik-gdc/net-amazon-s3 that referenced this issue Jul 10, 2018

Sanity object uris to avoid invalid signature (issue rustyconover#28)
Signature 4 documentation and test suite says that sequence of multiple
slashes should reduced to one (get-slashes test).

Although V4Implementation follows that performing such request causes
invalid signature error.

ranguard added a commit that referenced this issue Jul 10, 2018

Merge pull request #30 from branislav-zahradnik-gdc/master
Sanity object uris to avoid invalid signature (issue #28)
@ranguard

This comment has been minimized.

Collaborator

ranguard commented Jul 10, 2018

https://metacpan.org/release/LLAP/Net-Amazon-S3-0.83 - please comment if this does not fix it

@ranguard ranguard closed this Jul 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment