goauthentik / goauthentik/authentik
Add reason for model_updated of a user after authentik upgrade
Open
area:backend
bug
bug/confirmed
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 644
Description
After authentik has been upgraded you might be running a different django version which might have more rounds in password hashes, which causes the password hash in the model to be updated.
This is correct behaviour, however in our events system we don't capture the reason for this, so after upgrading you'll just see changed users with no obvious difference.
Contributor guide
Assessment
This issue has not been assessed yet.