Authentik 2026.8.0: stricter proxy headers, clean upgrade from 2026.5

released
lab run
upgraded from
2026.5.8
guest
Ubuntu 26.04 VM
tested
yes, in our lab

Summary

2026.8.0 is a large feature release. The GitHub notes for this tag are mostly a list of last-minute fixes and doc changes since 2026.8.0-rc7, and link to the full release notes.

Reported new features (from the 2026.8 release notes): access requests and agent accounts (Enterprise), user switching in one browser, object attributes, expiring policy bindings, OAuth token exchange and dynamic client registration, a Base URL system setting, PostgreSQL pooler support, and a Rust rewrite of the server entrypoint and proxy outpost.

Fixes in this tag include: SCIM group membership removals, deactivated users now have all sessions deleted, back-channel logout on deactivation, the query string kept after proxy-outpost login, and a missing csrf_exempt on dynamic client registration.

Breaking changes and deprecations

Reported in the release notes (not all tested by us):

  • Forwarded headers: X-Forwarded-Proto, X-Forwarded-Host and X-Forwarded-For are now honored only from trusted proxy networks. List every direct connection source in AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS. If you get this wrong, expect HTTPS treated as HTTP, mixed content, endless loading or login failures.
  • hash_password command no longer takes the password as an argument. Use the hidden prompt or pipe it in.
  • WebAuthn “Prevent duplicate devices” option removed.
  • Base URL: set the new Base URL system setting now. It becomes required in 2026.11.
  • Task statuses: tasks that log errors now show as errors or warnings, so failures that were hidden may appear.
  • Deprecated: AUTHENTIK_POSTGRESQL__CONN_OPTIONS and its replica equivalent.
  • Outposts must run the same version as the server.

Tested in our lab

We tested a Docker Compose install of 2026.5.8 (the newest 2026.5 patch we found) and upgraded it to 2026.8.0. Compose and .env came from the official docs. We created a test user with a password, an application, and an API token before upgrading.

  • Both versions started healthy. After the upgrade the server and worker took under two minutes to report healthy.
  • The API reported 2026.8.0. The test user, the application and the API token all survived, and the test user’s password still checked out.
  • The login flow and admin UI answered with HTTP 200.
  • No error or critical log lines after the upgrade. There were three warnings, all about the Base URL not being set (see above).

Not tested: reverse proxy and trusted-proxy behaviour (we hit authentik directly), outposts, Enterprise features, SSO integrations, the Rust proxy outpost, and any large database. We upgraded from a fresh, small install only.

Note: the current official compose.yml already points at 2026.8.5, so we pinned AUTHENTIK_TAG=2026.8.0 to test this exact release.

Lab log

$ docker compose up -d   # AUTHENTIK_TAG=2026.5.8 in .env
$ curl -s -H "Authorization: Bearer [redacted]" localhost:9000/api/v3/admin/version/
{"version_current":"2026.5.8","version_latest":"2026.8.5","version_latest_valid":true,"build_hash":"","outdated":true,"outpost_outdated":false}
$ docker compose down
[...]
$ sed -i "s/^AUTHENTIK_TAG=.*/AUTHENTIK_TAG=2026.8.0/" .env
$ docker compose pull -q
$ docker compose up -d
[...]
$ docker compose ps --format "{{.Service}} {{.Status}}"
postgresql Up 2 minutes (healthy)
server Up 2 minutes (healthy)
worker Up 2 minutes (healthy)
$ curl -s -H "Authorization: Bearer [redacted]" localhost:9000/api/v3/admin/version/
{"version_current":"2026.8.0","version_latest":"2026.8.5","version_latest_valid":true,"build_hash":"","outdated":true,"outpost_outdated":false}
$ curl -s -H "Authorization: Bearer [redacted]" "localhost:9000/api/v3/core/users/?search=labuser" | grep -o "\"username\":\"labuser\""
"username":"labuser"
$ curl -s -H "Authorization: Bearer [redacted]" localhost:9000/api/v3/core/applications/ | grep -o "\"slug\":\"[a-z-]*\""
"slug":"lab-app"
$ curl -s -o /dev/null -w "login page %{http_code}\n" localhost:9000/if/flow/default-authentication-flow/
login page 200
$ curl -s -o /dev/null -w "admin ui %{http_code}\n" -L localhost:9000/if/admin/
admin ui 200

Reported by others

We did not review issue trackers or forums for this release. The only reported information above comes from the official release notes.

Verdict

Wait (for the latest patch). In our small test the upgrade from 2026.5.8 was uneventful. But 2026.8.5 is already out, so there is little reason to install 2026.8.0 itself. If you upgrade, take the latest 2026.8.x, check your reverse proxy and AUTHENTIK_LISTEN__TRUSTED_PROXY_CIDRS first, and set the Base URL.

sources