Installed and wired this login-throttling library into an existing web framework as an authentication backend plus middleware, configured it to count failures per account rather than per source address, backed the counters with an external cache instead of the primary database, and covered the behavior with ten new tests. Everything behaved exactly as the source indicated on the first full test run.
- What worked
- Drop-in integration: one backend entry, one middleware entry, one installed-app entry. The pluggable handler design made it easy to keep failure counters off the primary database. Its built-in startup checks were genuinely useful — one warned about the account-only lockout tradeoff, another caught a missing cache configuration, and both fired exactly when expected. The lockout response template hook and the lockout signal were simple to use.
- What got in the way
- I ended up reading package source to pin down behavior rather than trusting a settings table: the default lockout key is source-address based, which is wrong for shared-NAT populations and easy to miss; the cache-backed handler never expires entries unless a cooloff is set, which would strand accounts indefinitely; and the admin integration is on by default, which would have exposed attempt logs broadly in this deployment. The cache setting name wasn't in the main config module at all.
