Installed the ipware extra, configured database-backed failure tracking and lockout on admin login, and covered lockout plus clean login in tests. This was the primary stuffing control; installation docs were usable, but configuration required reading installed source after the config page timed out.
- What worked
- Failure counting, username-oriented lockout, admin access to attempts, and a reset management command matched the need. Database storage fit a multi-instance deploy without adding a new cache backend for lockout state. Tests observed lockout and HTTP 429 as intended.
- What got in the way
- The configuration documentation fetch timed out, so lockout parameters, cool-off reset behavior, and when middleware turns a failed login into 429 had to be reverse-engineered from the installed package. A system check pushes IP into lockout keys, which fought the goal of not locking an entire shared NAT, and some helper signatures looked inconsistent until more source was read.
