terraform-authentik/config/permissions/akP-arrstack-user.yaml at 5f4b3557c17c445ca20f344d49b91e25f26aeeda - terraform-authentik - Gitea

unkin/terraform-authentik

Files

T

unkin-agent e7c1f561f1

ci/woodpecker/pr/pre-commit Pipeline was successful

Details

ci/woodpecker/pr/plan Pipeline failed

Details

add arrstack oauth app + per-app access groups

Add the Authentik OIDC application that fronts the arrproxy media front door
at arrstack.unkin.net, plus the per-app entitlement groups arrproxy reads from
the user's groups claim to decide which backends (sonarr/radarr/prowlarr) a
user may reach.

- config/providers_oauth2/arrstack.yaml: confidential oauth2 client
  client_id=arrstack, litellm-style auth/invalidation flows, client_secret
  from Vault kv kubernetes/namespace/arrstack/default/oauth-credentials,
  openid/email/profile scopes, redirect https://arrstack.unkin.net/oauth2/callback,
  launch https://arrstack.unkin.net/. The module always attaches the estate's
  hierarchical ak_groups scope mapping, so the front door emits the groups claim.
- config/permissions/akP-arrstack-user.yaml: front-door gate (application: arrstack).
- config/permissions/akP-arrstack-{sonarr,radarr,prowlarr}.yaml: per-app
  entitlements, unbound (no application) so they only surface in the ak_groups
  claim for arrproxy to authorize backends.
- config/roles/akR-arrstack-user.yaml: full media role nesting all four.
- akR-global-admin: also nests the arrstack front door + all per-app perms.

2026-08-16 15:00:05 +10:00

5 lines

258 B

YAML

Raw Blame History

 # Permission group akP-arrstack-user (name = filename). Front-door access to the
 # arrstack application: bound to the arrstack oauth2 app, so only members of this
 # group (or any role that nests it) can complete OIDC to the front door.
 application: arrstack