goauthentik / goauthentik/authentik
Upgrades recreate bootstrap defaults and restore deleted akadmin
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 644
Description
## What
upgrades silently re-create bootstrap defaults (renamed authentik Admins group / deleted akadmin user).
## Want
- Upgrades silently re-create bootstrap defaults (renamed authentik Admins group / deleted akadmin user)
## Ideas this came from
- [#20917 Upgrading re-inserts formerly renamed `authentik Admins` group](https://github.com/goauthentik/authentik/issues/20917) — When upgrading authentik recreates the authentik Admins group with factory settings, when it was renamed before upgrading, e.g. from authentik Admins to authent
- [#23045 akadmin (bootstrap) user is silently recreated during upgrades after being deleted](https://github.com/goauthentik/authentik/issues/23045) — When installing authentik, a default bootstrap admin account (akadmin) is created. As part of standard security hardening, database cleanup, and compliance prac
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reproducing an upgrade after renaming the authentik Admins group and deleting the akadmin user, then trace the upgrade handling for bootstrap defaults. Done means upgrades preserve those changes and do not silently recreate either default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100