-
Notifications
You must be signed in to change notification settings - Fork 282
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] Lots of waring message No 'Basic Authorization' header, send 401 and 'WWW-Authenticate Basic'
in log
#3273
Comments
[Triage] Thank you for filing this issue. This message is a warning message that is expected when you run with the SAML endpoint configuration you are using. This is a response from not having a Basic auth header (you have none because you are using SAML). You can disregard this message. We can follow-up this issue by making a change so that this log is TRACE/DEBUG instead of WARNING level. Then you should not see this output. |
…n' header, send 401 and 'WWW-Authenticate Basic' to trace
…n' header, send 401 and 'WWW-Authenticate Basic' to trace Signed-off-by: Priyank Bagrecha <[email protected]>
…n' header, send 401 and 'WWW-Authenticate Basic' to trace Signed-off-by: Priyank Bagrecha <[email protected]>
#3364) ### Description Change warning message No 'Basic Authorization' header, send 401 and 'WWW-Authenticate Basic' to trace ### Issues Resolved - Resolves #3273 ### Check List - [ ] New functionality includes testing - [ ] New functionality has been documented - [X] Commits are signed per the DCO using --signoff By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). --------- Signed-off-by: Priyank Bagrecha <[email protected]> Co-authored-by: Priyank Bagrecha <[email protected]>
#3364) ### Description Change warning message No 'Basic Authorization' header, send 401 and 'WWW-Authenticate Basic' to trace ### Issues Resolved - Resolves #3273 ### Check List - [ ] New functionality includes testing - [ ] New functionality has been documented - [X] Commits are signed per the DCO using --signoff By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For more information on following Developer Certificate of Origin and signing off your commits, please check [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#developer-certificate-of-origin). --------- Signed-off-by: Priyank Bagrecha <[email protected]> Co-authored-by: Priyank Bagrecha <[email protected]> (cherry picked from commit a41638b) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
any update with a solution? |
@taltsafrirpx the log level have changed to trace, so you should not see those warning by default. |
We are using OpenSearch 2.10.0. We are seeing this log message hugely. Which version this was fixed? |
d7d8472 |
For information just migrated my cluster to 2.11.1 and got log as warning with SAMl configuration. |
It's probably the order of the backens that's playing a role here. We are going to switch those so openid comes first and see what happens. |
In my case if i place SAML auth first it is breaks my basic auth. Also i open new issue. |
What is the bug?
When i enable both SAML and basic auth and login with SAML, there have lots of basic auth warning message
[2023-08-31T13:35:04,053][WARN ][o.o.s.h.HTTPBasicAuthenticator] [bcd07463160c] No 'Basic Authorization' header, send 401 and 'WWW-Authenticate Basic'
printed in OpenSearch log fileHow can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
Don't print warning message or should this be debug level
What is your host/environment?
Do you have any screenshots?
enable both SAML and basic
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: