We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Support password authentication in the Solr plugin, using Basic HTTP Authentication.
The Solr plugin should work with Solr instances with enabled authentication.
401 status code when the plugin tries to request Solr node with enabled authentication.
200 status code
Solr nodes, especially in prod environment, often use the authentication.
The text was updated successfully, but these errors were encountered:
Agreed, we should include the regular HTTP options along with this:
## Optional HTTP Basic Auth Credentials # username = "username" # password = "pa$$word" ## Optional TLS Config # tls_ca = "/etc/telegraf/ca.pem" # tls_cert = "/etc/telegraf/cert.pem" # tls_key = "/etc/telegraf/key.pem" ## Use TLS but skip chain & host verification # insecure_skip_verify = false ## Amount of time allowed to complete the HTTP request # timeout = "5s"
Sorry, something went wrong.
I've changed solr.go in order to have authenticated access and tested it with my Solr instances. May I push a request to some branch?
Yes, create a fork of this repo and then push it to a branch on the fork, then you can create the pull request from there.
#5832
Closed in #5832
No branches or pull requests
Feature Request
Support password authentication in the Solr plugin, using Basic HTTP Authentication.
Proposal:
The Solr plugin should work with Solr instances with enabled authentication.
Current behavior:
401 status code when the plugin tries to request Solr node with enabled authentication.
Desired behavior:
200 status code
Use case:
Solr nodes, especially in prod environment, often use the authentication.
The text was updated successfully, but these errors were encountered: