Fixed: Issue in AWS Signature v4 query parameters encoding at operation List-S3-Object

[megel]

Fixed and issue in AWS Signature v4 query parameters encoding at operation List-S3-Object.

Issue Details

Parameter prefix with special characters such as / caused an SignatureDoesNotMatch issue in AWS Signature v4.
The Error Message was:

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>AKIAXUTJO2VJ2B6CSFXA</AWSAccessKeyId><StringToSign>AWS4-HMAC-SHA256
20250303T081339Z
20250303/eu-central-1/s3/aws4_request
56f5af14e64431afcdcd5ec7481ac047cd5ea3bce5733aee8e54ecdfbe2e5ffd</StringToSign><SignatureProvided>917d9c3ea4f350c29299f37df7ac0208420216c3bc07882cb4f53075922dbff2</SignatureProvided><StringToSignBytes>....</StringToSignBytes>
<CanonicalRequest>GET
/
bucketlist-type=2&amp;prefix=folder-with-space%2FShared-Documents
host:my-powerapps-demo-bucket.s3-eu-central-1.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20250303T081339Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855</CanonicalRequest>
...

Tests:

Put S3 Object

With Text Files:

With Binary Content:

List S3 Object

Get S3 Object

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[vmanoharas]

Dear Partner

I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.