S3 Using Document Storage Error Occurs When Saving Documents with Japanese

chanzone-khm

I have configured the Document Storage feature to save documents to S3.
However, when attempting to upload a document with a Japanese title, the following error occurs. (English title can be uploaded successfully.)
Could you please provide guidance on the cause of this issue and how to resolve it?

~~~~
Caused by: java.lang.RuntimeException: <?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>A**********</AWSAccessKeyId> 
~~~~

Environment Details:

S3 Bucket Region: ap-northeast-1

Thank you for your support.

Alexander Suter

chanzone-khm So I guess other documents are working which has no Japanese character?

chanzone-khm

Files with English titles can be uploaded.
Files with Japanese titles cannot be uploaded and an error occurs.

I tried to attach the actual files, but an error occurred and I could not attach them, so I am attaching images.
Each file will contain only the letter “a”.
As you can see in the image, the document with the error has Japanese in the name title.

Alexander Suter

chanzone-khm I thought you speak about the content of the file (title), but you are talking about filenames. Thanks for clarification.

This is somehow funny. You can't upload the document to Axon Ivy but also cannot upload to this community forum (it's not ivy based - believe me 😁).

Probably, this is a general issue in Axon Ivy and maybe not dedicated to S3. I will check today.

Alexander Suter

chanzone-khm I found the problem. There was a little issue with signing the request. For more details see here:
https://github.com/axonivy-market/amazon-aws4-authenticator/pull/32

The fix will be part of Axon Ivy 12.0.1 LTS, which is currently planned for next week. You already can try out tomorrow our 12.0 nightly build.
https://dev.axonivy.com/download/nightly-12.0

Alexander Suter

Alexander Suter I could reproduce it and can confirm that this error is only related to S3. I will try to find a solution for it.

Alexander Suter

I found some other characters which still do not work. Need to investigate further.

chanzone-khm

Thank you so much for your prompt response and support. I plan to check this in the next version.

Alexander Suter

chanzone-khm I was able to improve the implementation. Hopefully it works now properly for all characters 👍