-
Notifications
You must be signed in to change notification settings - Fork 249
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
no auth scheme matched auth scheme options error when using no_credentials
with put object
#878
Comments
The S3 model doesn't state which operations work without credentials, so I did some guess work in the fix for #864 and chose |
What I'm after is an equivalent of |
Working on a fix. I'm going to open up all the S3 operations to |
In #2907, I created an allow list of S3 operations to add `@optionalAuth` to, but this turns out to be too restrictive, as seen in awslabs/aws-sdk-rust#878. This PR restores the original middleware behavior of allowing optional auth for all S3 operations. ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
A fix for this will be included in the next minor release. |
Just tested the newly released |
|
My bad. I merged the fix into our main branch instead of the patch release branch, so it didn't go out with 0.31 😞 |
Just a heads up, we're exercising our release infrastructure, so the next couple weeks or so of releases aren't going to include this fix. It will go out after we cut a non-patch release of smithy-rs. |
This is going out in 0.35 (currently queued up to release) |
|
Verified fixed in 0.35 |
Describe the bug
when using no_credentials() aws-sdk-s3 throws
no auth scheme matched auth scheme options. This is a bug. Please file an issue.
, same as #864 but only occurred in write operations likeput_object
.Expected Behavior
Disable credentials and signing.
Current Behavior
errors with "no auth scheme matched auth scheme options. This is a bug. Please file an issue."
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
Ubuntu 22.04
Logs
The text was updated successfully, but these errors were encountered: