R de Ren
33a794e35d
New stack:
- stacks/oauth2-proxy/ — per-app sidecars (mlflow, portainer, rabbitmq)
that gate vhosts via nginx auth_request against Keycloak's wbd realm.
Native OIDC wired into:
- grafana (generic_oauth, role-attribute-path → Admin/Editor/Viewer)
- jupyterhub (oauthenticator.GenericOAuthenticator)
- node-red (passport-openidconnect; in-memory state store + users()
resolver because adminAuth doesn't expose req.session)
- jenkins (oic-auth plugin via JCasC; matrix-auth for authz; setup
wizard suppressed; custom image with plugins.txt)
Infra fixes uncovered while bringing the above online:
- nginx-proxy: bump proxy_buffer_size to 16k so oauth2-proxy callbacks
don't 502 on the JWT-bearing Set-Cookie header.
- nginx-proxy: add `resolver 127.0.0.11 valid=30s` so service names
re-resolve after sidecar recreates (was cross-wiring oauth2-proxy
upstreams after restart).
- jupyterhub: pass --allow-root to the singleuser spawner (hub runs as
root inside its container; jupyter-server refused root without flag).
- jupyterhub Dockerfile: install jupyterlab + notebook so
SimpleLocalProcessSpawner has something to launch.
- node-red Dockerfile: install passport-openidconnect into the image
so settings.js can require() it.
- portainer: pre-seed local admin via --admin-password=<bcrypt-hash>
so the 5-minute "no admin → lockout" timer can never trigger.
- deploy.sh: restore executable bit (was 644 in repo).
Admin/viewer policy:
- Created realm role `app-admin` in keycloak wbd realm.
- Grafana maps app-admin → Admin (default Viewer).
- Jenkins matrix-auth grants r.de.ren Overall/Administer, authenticated
users get Overall/Read + Job/Read + View/Read.
- Node-RED: NODERED_ADMIN_USERS env list → permissions "*", others
["read"]. (TODO: switch to app-admin realm role.)
- JupyterHub: JUPYTERHUB_ADMIN_USERS env list. (Same TODO.)
- Gitea: r.de.ren pre-created as local admin; OIDC auto-links via email.
Docs:
- README, cloud/README, stacks/oauth2-proxy/README, and per-stack
READMEs updated to reflect the new state and remove resolved TODOs.
- cloud/.env.example gains all the new OIDC client + cookie-secret keys.
- cloud/README documents the full kcadm realm bootstrap, including the
hardcoded-audience mapper and post-logout redirect URIs that are
non-obvious gotchas.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jenkins
CI/CD for R&D pipelines. Cloud-only stack.
- Hostname:
ci.wbd-rd.nl - Network:
app(UI proxied via nginx) - Volume:
jenkins-home(config + job state + plugins) - Image: built locally (
cloud-jenkins:lts-jdk17) — upstream Jenkins LTS + pre-installed plugins. SeeDockerfile,plugins.txt.
Auth + authorization
Keycloak OIDC via the oic-auth plugin + JCasC (configuration-as-code). The setup wizard is suppressed (-Djenkins.install.runSetupWizard=false) and the security realm + authorization strategy come entirely from config/jenkins.yaml.
Permissions matrix
config/jenkins.yaml declares a globalMatrix authorization strategy:
| Principal | Permission |
|---|---|
USER:r.de.ren |
Overall/Administer (full admin) |
GROUP:authenticated |
Overall/Read + Job/Read + View/Read |
| anonymous | (no access — bounced to Keycloak) |
To promote another user, add a USER:Overall/Administer:<username> line to the matrix. Mapping the Keycloak app-admin realm role to admin via a ROLE: line (instead of per-user entries) is a TODO.
Plugins
plugins.txt:
configuration-as-code
oic-auth
matrix-auth
Add more as the team needs them — the Dockerfile re-runs jenkins-plugin-cli on build, so any addition to plugins.txt is picked up next time the image is rebuilt.
TODO
- Map
app-adminrealm role →Overall/AdministerviaROLE:entries (so admin promotion happens in Keycloak, not injenkins.yaml) - Agent strategy (DinD vs SSH vs K8s)
- Pipeline shared libraries + Job DSL seed jobs
- Gitea Actions runners (post-cutover) — or use Jenkins gitea webhooks