goauthentik / goauthentik/authentik

Forward-auth single application across multiple hosts

Open
#25,319 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 2h
Merged PRs (30d)
659

Description

## What

forward-auth (single application) across hosts: Caddy “not found” and multiple domains on one single-app provider.

## Want

- Forward-auth (single application) across hosts: Caddy “not found”
- Multiple domains on one single-app provider

## Ideas this came from

- [#12930 Error not found when I set up forward_auth (single application) with Caddy](https://github.com/goauthentik/authentik/issues/12930) — Describe your question I created a provider using the wizard. - Under Application Details: Name: Mailu Slug: mailu - Under Provider Type, I chose Forward Auth (
- [#16399 Forward Auth (single application) Multiple domain](https://github.com/goauthentik/authentik/issues/16399) — When setting up Forward Auth for a single application you need to create a new provider per separate domain. Which in general is good practice. However when dea

Contributor guide

Open the contributing guide

Research direction

Start by reading the linked issues #12930 and #16399, then inspect the current forward-auth single-application behavior. Define how Caddy's “not found” case and multiple domains should work before identifying the relevant implementation and tests; done means both requested scenarios are supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.