Configure Authentik env vars on deployment host and verify OIDC callback behind Caddy #8
Labels
No labels
bug
decision
docs
enhancement
integration
ops
security
tech-debt
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/BatteryStorageCalculator#8
Loading…
Reference in a new issue
No description provided.
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?
Item 1 of the Recommended Next Implementation Slice in
docs/implementation-audit.md.The backend OIDC implementation is complete and validates issuer, audience, expiration, signature, and login nonce. What has not been done is configuring it on the actual deployment host and confirming the callback works through the Caddy reverse proxy.
Env vars are documented in
README.md:AUTH_MODE,AUTH_REQUIRED,PUBLIC_APP_URL,SESSION_SECRET,OIDC_ISSUER_URL,OIDC_CLIENT_ID,OIDC_CLIENT_SECRET,OIDC_REDIRECT_URI.This is deployment/config work, not code work.
Sequencing (from the 2026-07-16 audit): do this after #28 (refuse to start OIDC mode with the default
SESSION_SECRET) so a misconfigured deploy fails at startup with a clear error rather than running with a forgeable session secret. #29 (CORS default) and #33 (full-stack default compose) touch the same deploy surface and are cheapest to verify in the same deployment pass.