Add Jellyfin OIDC provider, application and RBAC groups #19
Reference in New Issue
Block a user
Delete Branch "benvin/jellyfin-oidc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Jellyfin (task #3, auth) moves to Authentik SSO via jellyfin-plugin-sso (OIDC) so the web UI signs in through Authentik while native Jellyfin clients keep local/API auth. This is PR 1 of the multi-PR onboarding: the Authentik side only, following the existing provider-yaml pattern (client secret from Vault, no terraform-vault changes).
Changes
config/providers_oauth2/jellyfin.yaml: confidential OIDC clientjellyfinfor jellyfin.k8s.syd1.au.unkin.net; client_secret read fromkv/kubernetes/namespace/jellyfin/default/oauth-credentials; strict redirect URIs for both jellyfin-plugin-sso callback paths (/sso/OID/redirect/authentikand legacy/sso/OID/r/authentik); no role_mappings claim — the plugin requests theak_groupsscope and matches the hierarchical groups claim directlyakP-jellyfin-admin/akP-jellyfin-userbound to the jellyfin application (access gating per the two-tier RBAC model)akP-jellyfin-userunderakR-standard-userandakP-jellyfin-adminunderakR-global-adminNote for reviewer
The CI plan reads the Vault kv secret at plan time, so it stays red until
kv/kubernetes/namespace/jellyfin/default/oauth-credentialsis seeded with aclient_secretkey (agent Vault access was blocked this session; seed command posted in the task summary).