Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

S3GeneratePresignedURL differs from cfaws implementation

Description

None

Environment

None

Attachments

1
  • 28 Sept 2023, 12:02 pm

Activity

Show:

Pothys - MitrahSoft 19 October 2023 at 15:12

I created a separate ticket for SSE algorithm issue.https://luceeserver.atlassian.net/browse/LDEV-4729 . I’ve now closed this ticket

Pothys - MitrahSoft 6 October 2023 at 08:33

From My perspective The SSE algorithm argument values AES256 and KMS are not supported in the S3GeneratePresignedURL() function. It throws an error.

<Error> <Code>SignatureDoesNotMatch</Code> <Message> The request signature we calculated does not match the signature you provided. Check your key and signing method. </Message> </Error>

Pothys - MitrahSoft 4 October 2023 at 11:51

Added the testcase for this ticket.
PR : https://github.com/lucee/extension-s3/pull/16

Zac Spitzer 4 October 2023 at 08:55

Michael Offner 28 September 2023 at 12:11

please extend the test case tests/functions/S3GeneratePresignedURL.cfc in the S3 Repo with tests for the new arguments.

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Created 26 September 2023 at 16:28
Updated 19 October 2023 at 15:12
Resolved 19 October 2023 at 15:12

Flag notifications