Dogfood: own Keycloak client for files-bao (back-channel logout coverage) #853

Open
opened 2026-10-06 21:56:56 +00:00 by Cordy · 0 comments
Owner

Parked, low priority (Nikola, 2026-10-06).

files.c0rdyceps.ch (cairn-enc) and files-bao.c0rdyceps.ch (cairn-openbao) share the Keycloak client cairn in realm cordyceps. A client takes only one back-channel logout URL, and it now points at cairn-enc (#839 dogfood check). So files-bao sessions aren't ended by Keycloak-side sign-outs; they only end by periodic re-check or expiry.

To do:

  • Create a client cairn-bao (public, PKCE S256, redirect https://files-bao.c0rdyceps.ch/auth/callback, the same groups mapper). Set its back-channel URL to http://cairn-openbao.cairn.svc.cluster.local/auth/backchannel-logout with "session required" on.
  • Add it to homelab-config k3s/keycloak/realm-configmap.yaml.
  • Change oidcClientId in the untracked cairn-openbao-config Secret (needs manual kubectl), restart, and re-run the Keycloak-side sign-out check.

Not autonomous: the Keycloak admin login and the Secret edit both need Nikola.

Parked, low priority (Nikola, 2026-10-06). files.c0rdyceps.ch (cairn-enc) and files-bao.c0rdyceps.ch (cairn-openbao) share the Keycloak client `cairn` in realm `cordyceps`. A client takes only one back-channel logout URL, and it now points at cairn-enc (#839 dogfood check). So files-bao sessions aren't ended by Keycloak-side sign-outs; they only end by periodic re-check or expiry. To do: - Create a client `cairn-bao` (public, PKCE S256, redirect `https://files-bao.c0rdyceps.ch/auth/callback`, the same `groups` mapper). Set its back-channel URL to `http://cairn-openbao.cairn.svc.cluster.local/auth/backchannel-logout` with "session required" on. - Add it to homelab-config `k3s/keycloak/realm-configmap.yaml`. - Change `oidcClientId` in the untracked `cairn-openbao-config` Secret (needs manual kubectl), restart, and re-run the Keycloak-side sign-out check. Not autonomous: the Keycloak admin login and the Secret edit both need Nikola.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#853
No description provided.