-
Notifications
You must be signed in to change notification settings - Fork 107
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
v4 GetObject Signing #262
Comments
This is also a problem for me, and I do not know how to fix it either. |
I've had several users report S3 compatible services that seem to not work with V2 authorization and so I tried switching my program to use V4. GetObject from aws with V4 works for me. I wonder what I'm doing differently? I tried both path-style and request-style, to us-eastern. |
i got same problem |
some body help? |
this work `s3SignQuery S3Query{..} S3Configuration{ s3SignVersion = S3SignV4 signpayload,s3UseUri = True, .. } sd@SignatureData{..}
` |
The headers that are used to sign the
GetObject
do not work. See https://docs.aws.amazon.com/general/latest/gr/sigv4-create-string-to-sign.html and https://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.htmlThe requests fails with (note the StringToSign section):
While the Debug mode gives:
Obviously this results in a missmatch and the reported
SignatureDoesNotMatch
error. I tried to build the headers myself, but couldn't get it to work, as I am not familiar with the library.My test code gets the first 3 parameters correctly (see function
stringToSign
), but I couldn't get the hash to work. Can someone help me here?The text was updated successfully, but these errors were encountered: