Skip to content
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

S3 signature is not calculated correctly #15

Closed
zitmen opened this issue Nov 6, 2023 · 4 comments
Closed

S3 signature is not calculated correctly #15

zitmen opened this issue Nov 6, 2023 · 4 comments

Comments

@zitmen
Copy link
Contributor

zitmen commented Nov 6, 2023

Hi,

I am testing with S3 compatible storage (Minio) and I am experiencing issues where I am getting 403 Forbidden during authentication. Error code is SignatureDoesNotMatch.
I have found 2 causes:

  1. if endpoint contains port other than 80 or 443, the port must be included in the host header
  2. if the path ends with a path separator it must not be url encoded (I verified this issue also with AWS S3)

Best,
Martin

@zitmen
Copy link
Contributor Author

zitmen commented Nov 21, 2023

Actually it has not been fixed correctly as I still can't connect to my local minio instance due to incorrect signature

@zitmen zitmen reopened this Nov 21, 2023
@aloneguid
Copy link
Owner

How are you connecting? I've added a factory method for Minio for convenience, it works on my local network with custom port.

@zitmen
Copy link
Contributor Author

zitmen commented Nov 21, 2023

I did use the new factory. I am going to investigate tomorrow and if I find the root cause, I will share.

@zitmen
Copy link
Contributor Author

zitmen commented Nov 22, 2023

My appologies, I executed my integration tests with incorrect configuration yesterday.
Everything seems to work well now, so I am closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants