website/docs: Correct the forward authentication configuration template for Caddy (#11012)
Correct the forward authentication configuration template for Caddy The directives were not executed in the given order, but instead, using the implicit sequence defined in https://caddyserver.com/docs/caddyfile/directives#directive-order. Surrounding the directives with route {} fixes this. Signed-off-by: Andreas <43118918+eulores@users.noreply.github.com>
This commit is contained in:
@ -2,22 +2,25 @@ Use the following configuration:
|
|||||||
|
|
||||||
```
|
```
|
||||||
app.company {
|
app.company {
|
||||||
# always forward outpost path to actual outpost
|
# directive execution order is only as stated if enclosed with route.
|
||||||
reverse_proxy /outpost.goauthentik.io/* http://outpost.company:9000
|
route {
|
||||||
|
# always forward outpost path to actual outpost
|
||||||
|
reverse_proxy /outpost.goauthentik.io/* http://outpost.company:9000
|
||||||
|
|
||||||
# forward authentication to outpost
|
# forward authentication to outpost
|
||||||
forward_auth http://outpost.company:9000 {
|
forward_auth http://outpost.company:9000 {
|
||||||
uri /outpost.goauthentik.io/auth/caddy
|
uri /outpost.goauthentik.io/auth/caddy
|
||||||
|
|
||||||
# capitalization of the headers is important, otherwise they will be empty
|
# capitalization of the headers is important, otherwise they will be empty
|
||||||
copy_headers X-Authentik-Username X-Authentik-Groups X-Authentik-Email X-Authentik-Name X-Authentik-Uid X-Authentik-Jwt X-Authentik-Meta-Jwks X-Authentik-Meta-Outpost X-Authentik-Meta-Provider X-Authentik-Meta-App X-Authentik-Meta-Version
|
copy_headers X-Authentik-Username X-Authentik-Groups X-Authentik-Email X-Authentik-Name X-Authentik-Uid X-Authentik-Jwt X-Authentik-Meta-Jwks X-Authentik-Meta-Outpost X-Authentik-Meta-Provider X-Authentik-Meta-App X-Authentik-Meta-Version
|
||||||
|
|
||||||
# optional, in this config trust all private ranges, should probably be set to the outposts IP
|
# optional, in this config trust all private ranges, should probably be set to the outposts IP
|
||||||
trusted_proxies private_ranges
|
trusted_proxies private_ranges
|
||||||
|
}
|
||||||
|
|
||||||
|
# actual site configuration below, for example
|
||||||
|
reverse_proxy localhost:1234
|
||||||
}
|
}
|
||||||
|
|
||||||
# actual site configuration below, for example
|
|
||||||
reverse_proxy localhost:1234
|
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user