authentik/outpost
Jens Langhammer 4a94f515b3 root: add next branch 2021-02-18 21:24:34 +01:00
..
cmd/proxy outposts: update go module domain 2021-01-16 21:45:24 +01:00
pkg outpost: improve logging output, ensure fields match api server 2021-02-11 23:52:00 +01:00
.dockerignore
.gitignore
Makefile
README.md stages/consent: fix wrong widget for expire 2021-02-02 15:01:33 +01:00
azure-pipelines.yml root: add next branch 2021-02-18 21:24:34 +01:00
go.mod crypto: move certificate and key data to separate api calls to create events 2021-02-09 21:47:00 +01:00
go.sum crypto: move certificate and key data to separate api calls to create events 2021-02-09 21:47:00 +01:00
main.go
proxy.Dockerfile outposts: update pipeline 2021-01-16 21:49:30 +01:00

README.md

authentik outpost

CI Build status Docker pulls (proxy)

Reverse Proxy based on oauth2_proxy, completely managed and monitored by authentik.

Usage

authentik Proxy is built to be configured by authentik itself, hence the only options you can directly give it are connection params.

The following environment variable are implemented:

AUTHENTIK_HOST: Full URL to the authentik instance with protocol, i.e. "https://authentik.company.tld"

AUTHENTIK_TOKEN: Token used to authenticate against authentik. This is generated after an Outpost instance is created.

AUTHENTIK_INSECURE: This environment variable can optionally be set to ignore the SSL Certificate of the authentik instance. Applies to both HTTP and WS connections.

Development

authentik Proxy uses an auto-generated API Client to communicate with authentik. This client is not kept in git. To generate the client locally, run make generate.

Afterwards you can build the proxy like any other Go project, using go build.