-
Notifications
You must be signed in to change notification settings - Fork 146
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
RFE: Add support for LDAP auth in grafana #912
Comments
It could be just a configuration issue that should be cover in the documentation. |
This is a customer request for a feature to make this work out of the box |
LDAP needs configuration, it cannot be out of the box, a user will need to configure it. |
Grafana supports LDAP for use authentication. You can read more about grafana support here: https://grafana.com/docs/grafana/latest/auth/ldap/ This patch adds a command line option `-P` to pass an ldap configuration file to Grafana. Note that to access your LDAP from Grafana you'll need to login as admin. Fixes scylladb#912 Signed-off-by: Amnon Heiman <[email protected]>
Grafana supports LDAP for use authentication. You can read more about grafana support here: https://grafana.com/docs/grafana/latest/auth/ldap/ This patch adds a command line option `-P` to pass an ldap configuration file to Grafana. Note that to access your LDAP from Grafana you'll need to login as admin. Fixes scylladb#912 Signed-off-by: Amnon Heiman <[email protected]>
Grafana supports LDAP for use authentication. You can read more about grafana support here: https://grafana.com/docs/grafana/latest/auth/ldap/ This patch adds a command line option `-P` to pass an ldap configuration file to Grafana. Note that to access your LDAP from Grafana you'll need to login as admin. Fixes scylladb#912 Signed-off-by: Amnon Heiman <[email protected]>
https://grafana.com/docs/grafana/latest/auth/ldap/
This is a request to add LDAP support to the authentication mechanism in Grafana instead of just supporting a user/pass auth mechanism.
The text was updated successfully, but these errors were encountered: