Authentik provider + groups one-time setup for OIDC login and client enrollment #17
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Code for OIDC login and the client portal is deployed and tested (#10, #12), but Authentik needs one-time admin setup (see header comment in
api/auth.js):/api/auth/callback), application "LisiLou Portfolio"lisilou-admingroup with Elysse (grants dashboard access)OIDC_*+SESSION_SECRETin both instances'api/.envUpdate: commit
c367758("Add idempotent Authentik setup script for issues #10/#12") automates steps 1–3 via the Authentik API — run it withAUTHENTIK_URL+AUTHENTIK_TOKENonce CT121 is confirmed reachable, then paste its printed output into step 4.Migrated from
docs/BACKLOG-2026-07-16.md(B3).Completed 2026-07-20 - see the comment on #12 for the full writeup (three bugs found and fixed in
scripts/authentik-setup.sh, verified end-to-end on both dev and prod).Design note on dev-vs-prod: this uses a single shared OAuth2 provider/application with both redirect URIs registered (
dev-lisilou.jerodrigged.comandlisilou.jerodrigged.com), rather than two separate providers - same photographer, samelisilou-admingroup, just two valid callback URLs.api/.envon each host has its ownOIDC_REDIRECT_URIand its ownSESSION_SECRET, sharing the sameOIDC_CLIENT_ID/OIDC_CLIENT_SECRET/OIDC_ISSUER. Verified working independently on both hosts via a disposable test admin account driven through the real authorization-code+PKCE flow.