Public: anyone can read this; nobody can change it.
germinate: Grafana SSO on daughters (roll onto the sealed OAuth client; Admin = this platform's operator) #134
trevato hit "application error" signing into a fresh daughter's Grafana with Forgejo SSO. Two defects, both in germination: Placeholder client forever.
stopped closed without shipping
commented
Merged as part of #135 (same finalize region; the front-door PR carried this commit). Closing.
Sign in to join this conversation.
new above
offline
trevato hit "application error" signing into a fresh daughter's Grafana with Forgejo SSO. Two defects, both in germination:
grafana-oauthis sealed withpending-registrationfirst; Flux starts Grafana;fork_register_grafana_oauthseals the real client id/secret later — butenvFromSecretis read ONCE at pod creation and nothing rolled the Deployment. Forgejo answered the authorize with 400 Client ID not registered (that page is the "application error"). Fix: the same finalize-time roll germinate already does for mcp, now for Grafana (best-effort).role_attribute_pathnamed the PARENT's operator (trevato), so on a daughter every SSO login was a Viewer and nobody could hold the Admin session/flow-api's forwardAuth needs. Fix: re-point it at the daughter's own admin at seal time (parent's RBAC shape, right name).Proven live on the test daughter (hot-fixed the same way): full OAuth round trip →
/api/user200 asplat,/api/user/orgsrole Admin,/api/org/users200.Separate, pre-existing (parent AND daughters):
monitoring/grafana-folder-aclCronJob fails every 2 min with ConnectionRefused to the Grafana Service — Viewer folder-scoping isn't being enforced. Own issue.