-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Ping Endpoint Should Respect Auth Configuration #10167
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I would still like to see this done. The current behavior goes against what I think a users expectations are. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions. |
@jjathman this fix will land in 1.7.9. |
Proposal: Enable Auth for Ping Endpoint
Current behavior: Currently, the /ping endpoint will return successfully when Influx is running with HTTP authentication turned on even if the client does not provide the basic auth credentials.
Desired behavior: Either make the /ping endpoint respect the HTTP auth setting or allow a configuration setting to turn this on.
Use case: Spring Boot uses the Influx Java driver which currently uses the ping endpoint to determine the health of Influx. However, if authentication is enabled on Influx but the client does not have it configured or it isn't configured correctly any queries or writes will fail. Having a successful ping and health check provides a false indication that there aren't any configuration issues on the client. I would like at least for a configuration option to force the /ping endpoint to respect auth settings.
The text was updated successfully, but these errors were encountered: