catborise 3210ef2eee fix(accounts): a username longer than the field is refused by the login form ... Django's login form gives the username its max_length after the field is built, so a longer username was not refused and reached authentication. django-axes then stored it in its 255-character column, which PostgreSQL refuses: a login with a 300-character username was a 500 (SQLite does not enforce the length). Both login forms, with and without OTP, now check the length, so such a username is a form error and never reaches authentication, the lockout or the Logs page. This also turns the PostgreSQL leg of CI green again: the S-16 test from #167 hit exactly this.		2026-10-23 16:06:10 +03:00
..
migrations	feat(logs): admin changes and logins are recorded on the Logs page	2026-10-23 10:30:48 +03:00
tests	fix(accounts): a username longer than the field is refused by the login form	2026-10-23 16:06:10 +03:00
__init__.py	Add logs and block for templates	2015-03-03 11:34:09 +02:00
apps.py	feat(logs): admin changes and logins are recorded on the Logs page	2026-10-23 10:30:48 +03:00
audit.py	fix(logs): a typed username cannot forge a record in the file log	2026-10-23 15:31:00 +03:00
models.py	feat(logs): admin changes and logins are recorded on the Logs page	2026-10-23 10:30:48 +03:00
urls.py	lint with black python. convert f style strings to old one. some small fixes	2020-11-05 12:34:31 +03:00
views.py	feat(logs): admin changes and logins are recorded on the Logs page	2026-10-23 10:30:48 +03:00