Repository navigation
Upgrade notes
auth.groups is now enforced at the gateway. With provider: keycloak, logged-in users outside the listed groups get a 403 (enforceAtGateway defaults to true). Check each app's auth.groups before upgrading. Requires Envoy Gateway v1.2.0+.
The
groupsclaim now carries full paths (/finance,/parent/child) for every app, so apps that read it themselves should expect the leading/. Users of apps that enforce groups are logged out once (the access-token cookie is renamed), and every app's Keycloak client is reprovisioned once.
Custom groups mappers belong in the NebariApp. Groups mappers added to the client by hand are deleted, with a GroupsMappersRemoved warning. A custom mapper must use full.path: "true"; the "false" example from the v0.1.2 docs now denies every request (GroupsClaimConflict).
See "Group-based access control" in docs/reconcilers/authentication.md for the full behaviour, and docs/troubleshooting.md if users start getting 403s.
What's Changed
- Publish the Nebari Pack Specification by @dcmcand in #187
- feat(auth): enforce auth.groups at the gateway by @dcmcand in #198
- fix(auth): auth.groups follow-ups from the #198 review by @viniciusdc in #209
- feat(auth): report each groups mapper deleted from the client by @viniciusdc in #214
- docs: correct auth events and reasons, and add auth.groups troubleshooting by @viniciusdc in #215
Full Changelog: v0.1.2...v0.2.0
Installation
Install the operator in your cluster:
kubectl apply -f https://github.com/nebari-dev/nebari-operator/releases/download/v0.2.0/install.yamlOr use the Docker image:
quay.io/nebari/nebari-operator:v0.2.0