Upgrade Path

authentik 2023.6.0 → 2023.8.0

3 versions, 1 with breaking changes, 1 required stop

Required stops

Version by version, oldest first

2023.6.1: no action items (1 version)

2023.6.2 2023-08-29

Full release notes for 2023.6.2

2023.8.0 2023-08-29

Breaking

  • Removal of PostgreSQL 11 support

As announced in the 2023.5 release notes (and postponed by a release), this release requires PostgreSQL 12 or newer. This is due to a changed requirement in a framework we use, Django.

This does not affect docker-compose installations (as these already ship with PostgreSQL 12), however it is still recommended to upgrade to a newer version when convenient.

For Kubernetes install, a manual one-time migration has to be done: Upgrading PostgreSQL on Kubernetes

  • Changed nested Group membership behavior

In previous versions, nested groups were handled very inconsistently. Binding a group to an application/etc would check the membership recursively, however when using user.ak_groups.all() would only return direct memberships. Additionally, using user.group_attributes() would do the same and only merge all group attributes for direct memberships.

This has been changed to always use the same logic as when checking for access, which means dealing with complex group structures is a lot more consistent.

Policies that do use user.ak_groups.all() will retain the current behavior, to use the new behavior replace the call with user.all_groups().

From docs.goauthentik.io/releases/2023.8#breaking-changes

Note

This release changes the PostgreSQL dependency to require Version 12 or later, which only affects Kubernetes installs. See here for more info on upgrading.

From docs.goauthentik.io/releases/2023.8#upgrading

Full release notes for 2023.8.0

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.