-
Notifications
You must be signed in to change notification settings - Fork 191
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
[BUG] Clear scroll request fails with sigv4 signature mismatch for java client 2.8.0 #712
Labels
bug
Something isn't working
Comments
Hello, any updates or hints about this issue ? We have got the same issue when using Opensearch in AWS Best regards, |
AFAIK nobody is working on this. Want to help?
|
Replacing |
5 tasks
12 tasks
12 tasks
[Catch All Triage - 1, 2, 3, 4] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
clearScroll
request to opensearch client fails with sigv4 signing mismatch:org.opensearch.client.opensearch._types.OpenSearchException: Request failed: [security_exception] The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
The Canonical String for this request should have been
'DELETE
/_search/scroll
... remaining request info...
How can one reproduce the bug?
How can one reproduce the bug?
Create an OpenSearchClient following instructions from here (https://opensearch.org/docs/2.7/clients/java/#connecting-to-amazon-opensearch-service) and then attempt to use the client's
clearScroll
API.I believe this is because it is a DELETE request with a body. The
search/scroll
method works as intended. Sending the request results in a sigv4 errorWhat is the expected behavior?
The
clearScroll
API call does not have a signature mismatchWhat is your host/environment?
Ubuntu 22.04
implementation 'org.opensearch.client:opensearch-java:2.8.0'
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: