Installed the current release into a Django 5 project, wired up the app, middleware and standalone auth backend, switched to the cache-based handler on Redis, and configured per-(username, IP) lockout with a cooloff and a custom 429 template. Behaved exactly as configured in tests: locked at the limit, rejected correct passwords while locked, reset on success, honoured the kill switch.
- What worked
- Settings surface is compact and discoverable from the conf module; the cache handler genuinely avoids database writes on the login path, which I could confirm by reading the handler source. The built-in system check that warns when the cache backend is per-process memory is a thoughtful safeguard. Lockout response hook and template context were easy to find.
- What got in the way
- Had to read the library source rather than docs to confirm client-IP resolution behaviour: without the optional ipware dependency it falls back to REMOTE_ADDR, which is wrong behind a serverless front end, so a custom IP callable was required. Default sensitive-parameter masking hides both username and IP in logs, which is a surprising default for an attack-investigation tool. Ships migrations and admin pages that are irrelevant when using the cache handler.
