Add Okta + Entra support to workload Grafana
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
The workload Grafana instances should conditionally support Okta or Entra authentication (and any other methods desired by customers). The grafana.ini config block in the helm chart supports an auth.okta and auth.azuread block. We should account for the default role users are assigned on login, some orgs may prefer viewer or editor.
Alternatively we could provide them simple basic auth credentials to start in lieu of the default admin credentials already present in each workload instance.
Full list of auth methods supported by Grafana: https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#authanonymous
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Helm chart's grafana.ini config block and review Grafana's supported authentication methods, including the linked documentation. Determine how Okta or Entra settings and the default login role should be selected per workload, and whether basic auth is an alternative. Done means the chosen authentication configuration and role behavior are supported without relying on the existing default admin credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, helm
- Domain
- authentication, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100