SSO: Wire Grafana → Keycloak OIDC #337
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform#337
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Standalone — scoped during platform SSO initiative (2026-05-04). Depends on platform realm ticket.
Repo
forgejo_admin/pal-e-platformUser Story
As a platform admin
I want to click through to Grafana from my dashboard and be automatically logged in
So that I can check metrics without a separate login
Context
Grafana has built-in generic_oauth support. Config goes in kube-prometheus-stack Helm values under
grafana.grafana.ini.auth.generic_oauth. The Keycloak session cookie from the initial pal-e-admin login means Grafana's redirect to Keycloak returns immediately with a token — no login form shown.File Targets
Files the agent should modify or create:
terraform/modules/monitoring/main.tf— add generic_oauth config to kube-prometheus-stack Helm valuesFiles the agent should NOT touch:
terraform/modules/keycloak/main.tf— realm managed separatelyAcceptance Criteria
Test Expectations
curl -s https://grafana.tail5b443a.ts.net/api/health | jq .Constraints
generic_oauth(not Grafana's dedicated Keycloak provider — it's deprecated)Checklist
Related
project-pal-e-platform— platform project