mirror of
https://github.com/grafana/grafana.git
synced 2024-11-24 09:50:29 -06:00
0cbbb43222
* Move the ReloadLDAPCfg function to the debug file Appears to be a better suite place for this. * LDAP: Return the server information when we find a specific user We allow you to specify multiple LDAP servers as part of LDAP authentication integration. As part of searching for specific users, we need to understand from which server they come from. Returning the server configuration as part of the search will help us do two things: - Understand in which server we found the user - Have access the groups specified as part of the server configuration * LDAP: Adds the /api/admin/ldap/:username endpoint This endpoint returns a user found within the configured LDAP server(s). Moreso, it provides the mapping information for the user to help administrators understand how the users would be created within Grafana based on the current configuration. No changes are executed or saved to the database, this is all an in-memory representation of how the final result would look like. |
||
|---|---|---|
| .. | ||
| auth_proxy | ||
| auth_proxy.go | ||
| auth_test.go | ||
| auth.go | ||
| dashboard_redirect_test.go | ||
| dashboard_redirect.go | ||
| headers.go | ||
| logger.go | ||
| middleware_basic_auth_test.go | ||
| middleware_test.go | ||
| middleware.go | ||
| org_redirect_test.go | ||
| org_redirect.go | ||
| perf.go | ||
| quota_test.go | ||
| quota.go | ||
| recovery_test.go | ||
| recovery.go | ||
| render_auth.go | ||
| request_metrics.go | ||
| request_tracing.go | ||
| testing.go | ||
| util.go | ||
| validate_host.go | ||