Upgrade Path

authentik 2022.3.1 → 2022.4.1

3 versions, 1 with breaking changes, 1 required stop

Required stops

Version by version, oldest first

2022.3.2: no action items (1 version)

2022.3.3 2022-03-21

Full release notes for 2022.3.3

2022.4.1 2022-04-12

Breaking

  • Removal of HTTP Basic authentication for API requests

For legacy reasons, authentik used to support HTTP-Basic authenticated requests, using the token as a password. This has been removed.

  • Removal of deprecated context in Expression policies used in prompt stages

Before this version, you could use both context['*field_name*'] and context['prompt_data']['*field_name*']. The former one has been removed as it could overwrite other data in the context if the field name is the same as another context value.

  • Added name field for invitations

Invitations now require a name, used to better identify their purpose.

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

Full release notes for 2022.4.1

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.