authentik forward auth with Traefik
Putting authentik in front of applications behind Traefik with the forwardAuth middleware: Docker Compose labels, Kubernetes ingress routes, response headers and single-application versus domain-level mode.

Protecting applications that cannot speak OIDC or SAML with authentik's proxy outpost behind a specific reverse proxy, and deploying and running outposts on Docker or Kubernetes.
Putting authentik in front of applications behind Traefik with the forwardAuth middleware: Docker Compose labels, Kubernetes ingress routes, response headers and single-application versus domain-level mode.
Protecting applications served by NGINX with authentik through auth_request: the outpost location, headers passed upstream, redirects to login and Kubernetes ingress-nginx annotations.
Using Caddy's forward_auth directive with the authentik outpost: the outpost path, copying identity headers to the upstream application and TLS handled by Caddy.
Checking requests against authentik from Envoy or an Istio mesh with external authorization: the outpost as ext_authz service, which paths go to authentik and per-application policies.
Protecting applications behind HAProxy with the authentik outpost: request routing for the outpost path, authentication checks and headers to the backend.
Choosing between one provider per application and one provider for a whole parent domain: per-application policies, cookie domains, authorization prompts and the trade-off in access control.
Passing the signed-in user to applications that trust HTTP headers: user and application headers the proxy outpost sets, additionalHeaders on users and groups, custom dynamic headers and keeping the app unreachable except through the proxy.
Running proxy, LDAP, RADIUS and RAC outposts in Kubernetes: the built-in Kubernetes integration that authentik manages, replicas, namespaces and ingress settings, or manual deployments with your own manifests.
Running authentik outposts next to applications on Docker hosts: the Docker integration that creates containers automatically, manual Compose deployments with an outpost token, networks and image sources.
Understanding the outpost built into the authentik server: what it serves, shared metrics, when a standalone proxy outpost is better, and the hardening advice to disable it if unused.
Letting users log in to Linux servers with authentik credentials through SSSD and the LDAP outpost: service account and search group, LDAPS, and what is not supported such as sudo rules, automount and Kerberos.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.