Grafana oauth
Implement Helmholtz AAI Auth and Syncing of User Projects to Organizations/Teams on Grafana Login
What has been changed in TSM-orchestration?
- added
worker-grafana-user-orgstodocker-compose.ymlanddocker-compose-dev.yml - removed provisioned default datasource from
grafana/provisioningand the respective ENVVARS fromvisualization - added IF condition in proxy location
/visualization- check if
request_uri = "/visualization/login/generic_oauth"andhttp_sec_fetch_site = "same-origin" - if true then redirect request to
/frontend/oidc/login/?next=/visualization/login/generic_oauth
- check if
User experience of logging into TSM-Grafana:
- user clicks on
Sign in with Helmholtz-AAI- gets redirected to Frontend Oauth login
- doesn't see anything from the Frontend because Helmholtz-AAI oauth process is started immediately
- user finishes Oauth login
- Frontend publishes the
eduperson_principal_nameandeduperson_entitlementto the MQTT broker - dispatcher action in related MR tsm-dispatcher!71 (merged) sets user memberships in grafana organizations/teams
- user is immediately redirected to Grafanas Oauth Login
- Frontend publishes the
- user gets automatically logged in to Grafana without any other clicking needed with memberships derived from users
eduperson_entitlement- might need to reload to see all permissions, if logging in to grafana for the first time
Edited by Joost Hemmen