feat: initial authentik server commit#336
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds an initial authentik local-development stack (Docker Compose) plus several Authentik blueprint YAML exports for authentication, enrollment, and recovery flows.
Changes:
- Added
authentik/compose.ymlto run Postgres + authentik server/worker locally. - Added blueprint YAMLs defining authentication, enrollment (email verification), and recovery (email + MFA verification) flows.
- Added an
authentik/.gitignoreto keep local data/templates/certs out of git.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| authentik/compose.yml | Introduces a docker-compose stack for authentik + postgres (currently has YAML structure issues). |
| authentik/blueprints/50-opensource-authentication-flow.yaml | Adds a generated authentication flow blueprint (password + MFA + login bindings). |
| authentik/blueprints/10-flows-recovery-email-mfa-verification.yaml | Adds a recovery flow blueprint with email verification and MFA validation stages. |
| authentik/blueprints/10-flows-enrollment-email-verification.yaml | Adds an enrollment flow blueprint with prompts and email verification (with an ordering issue). |
| authentik/.gitignore | Ignores local authentik data, templates, and cert directories. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
cmyers-mieweb
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Copilot Summary
This pull request introduces several major updates to the
authentikdirectory, focusing on infrastructure setup and the addition of blueprint YAML files for authentication, enrollment, and recovery flows. The most significant changes include the addition of a Docker Compose configuration for local development, the creation of reusable flow blueprints for enrollment and recovery (including email and MFA verification), and a comprehensive authentication flow blueprint. Additionally,.gitignorewas updated to exclude data, templates, and certificates directories.Infrastructure and Configuration:
compose.ymlfor Docker Compose, definingpostgresql,server, andworkerservices with required environment variables, health checks, volume mounts, and dependencies for local development of authentik..gitignoreto exclude/data/,/custom-templates/, and/certs/directories, preventing sensitive or generated files from being committed.Blueprints for Flows:
10-flows-enrollment-email-verification.yaml, a blueprint defining a default enrollment flow with staged prompts for username, password, name, and email, including email verification and user activation.10-flows-recovery-email-mfa-verification.yaml, a blueprint for a recovery flow that includes identification, email verification, MFA validation, password reset, and user login, with policy bindings for conditional stage execution.50-opensource-authentication-flow.yaml, a comprehensive blueprint for an authentication flow supporting multiple backends, password and MFA stages, identification, and integration with enrollment and recovery flows. Includes custom policy bindings for conditional stage execution.