authentik 2023.4.0 → 2023.5.0
3 versions, 1 with breaking changes, 1 required stop
Required stops
- 2023.4.3
Latest 2023.4.x release.
Upgrade sequence: Upgrades must follow the sequence of major releases; do not skip directly from an older major version to the most recent version.
Always upgrade to the latest minor version (
.x) within eachmajor.minorversion before upgrading to the next major version. For example, if you're currently running2025.2.1, upgrade in the following order:- Upgrade to the latest
2025.2.x. - Then to the latest
2025.4.x. - Finally to the latest
2025.6.x.
Outposts: The version of the authentik server and all authentik outposts must match. Ensure that all outposts are upgraded at the same time as the core authentik instance.
Source: https://docs.goauthentik.io/install-config/upgrade/#important-considerations (checked 2026-09-28)
- Upgrade to the latest
Version by version, oldest first
2023.4.1: no action items (1 version)
2023.4.2: released after 2023.5.0; not on this route
2023.4.3 2023-07-06
Required stop
2023.5.0 2023-05-16
Breaking
- Deprecation of PostgreSQL 11 support
The next release of authentik will only support PostgreSQL 12 and newer. Upgrading can be done with https://github.com/tianon/docker-postgres-upgrade or by exporting the database and re-importing the database into a new PostgreSQL instance.
- Removal of deprecated LDAP fields
This version removes the deprecated LDAP fields goauthentik.io/ldap/active and goauthentik.io/ldap/superuser.
Additionally, any custom fields based on user attributes will only be represented with their sanitized key, removing any slashes with dashes, and removing periods.
- Renamed docker-compose environment variables
To better distinguish settings that configure authentik itself and settings that configure docker-compose, the environment variables AUTHENTIK_PORT_HTTP and AUTHENTIK_PORT_HTTPS have been renamed to COMPOSE_PORT_HTTP and COMPOSE_PORT_HTTPS respectively.
Release notes from github.com/goauthentik/authentik/releases, and the release notes on docs.goauthentik.io, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. authentik publishes one release-notes page per YYYY.M release on docs.goauthentik.io. Its “Breaking changes” section is quoted whole as “Breaking” on the first release of that line (YYYY.M.0; 2022.1 to 2022.8 started at YYYY.M.1), its “Deprecations” section as “Note”, and the opening paragraph of its “Upgrading” section as “Note” unless it only says “This release does not introduce any new requirements”. Fixes in patch releases (“Fixed in …”) are not quoted, and neither are GitHub release notes (lists of merged pull requests). Versions are covered from 2022.1.0. Required stops: the latest patch release of every YYYY.M line on the way, per the upgrade documentation.