You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.
I noticed that the basic auth credentials in /datasources/graphite/graphite.json (guest/guest) do not actually get authenticated.
I know that these credentials (guest/guest from .htpasswd) are used for the graphite (admin) dashboard, but how does Graphite as a datasource actually use authentication?
The text was updated successfully, but these errors were encountered:
Aha, I wonder if its an mistake from my side: We did a switch from our own home grown setup to use the default containers for Graphite. I should probably just remove that then.
For securing I use ipfw firewall, I'm gonna add some examples for that when I update the docs for setting up Graphite on AWS.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I noticed that the basic auth credentials in /datasources/graphite/graphite.json (guest/guest) do not actually get authenticated.
I know that these credentials (guest/guest from .htpasswd) are used for the graphite (admin) dashboard, but how does Graphite as a datasource actually use authentication?
The text was updated successfully, but these errors were encountered: