Closed wisdomleo closed 2 years ago
**Relate to amzn/selling-partner-api-models#703
https://github.com/amzn/selling-partner-api-models/issues/42**
Thanks michaellavoie !!!
michaellavoie commented on 1 May While we wait for an official fix, I was able to resolve the bug by running this find-replace on the generated swagger output: Find: var localVarPath = " Replace: var localVarPath = $"
@wisdomleo - have you created separate sdk clients for each API endpoint? like for feeds,orders,reports and referencing them? I'm trying to figure out if I can create one sdk client for all the APIs that are needed
{ "errors": [ { "message": "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
The Canonical String for this request should have been 'GET /reports/2021-06-30/reports/5189...
accept:application/json host:sellingpartnerapi-na.amazon.com x-amz-access-token:Atza|IwEBIH1z4kzFZFDtAm... ... ...SkxamYSj5zkiETz1jsgi x-amz-date:20211117T065625Z x-amz-security-token:FwoGZXIvYXdzEPj//////////wE... ... ...bbYgcBe7RohkuX7C3azLVsj8JhFvCk+LdMeg8IpmCV1qo=
accept;host;x-amz-access-token;x-amz-date;x-amz-security-token e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
The String-to-Sign should have been 'AWS4-HMAC-SHA256 20211117T065625Z 20211117/us-east-1/execute-api/aws4_request ee7c603bda80885d4a8ab9a7bc33414e43366d361d137619f169d4b7df0446c1' ", "code": "InvalidSignature" } ] }
access and signed normally on 'createReport' call, but met 'invalid signature' error...
anybody knows why? /going crazy//going crazy//going crazy/
C# code as below:
region Generating the x-amz-security-token Header