FEATURE REQUEST: Setting to control a closed User account

[daz-williams]

Is your feature request related to a problem? Please describe.
When a User requests to close their account, we set the is_active field to False in the Django Default User Model.
This prevents sign-in.
With an out of the box Axes setup, Axes treats this as a Failed Login attempt.
Error in logs: AXES: User login failed, running database handler for failure.
I am unable to implement a Custom User Login as Axes processes the login request before it is processed in the custom user login class.

Describe the solution you'd like
An Axes setting that checks if the is_active user field is set to False and responds with a relevant flag "User Account Inactive" or similar.

Describe alternatives you've considered
I tried the example view on the Axes Custom Installation page and it does not take into account the is_active field.
Axes Link: https://django-axes.readthedocs.io/en/latest/5_customization.html

Additional context
Axes rocks!!! Thank you for a great product!

[aleksihakli]

Hey! Sounds like a good improvement, please feel free to open a PR for this.

[kim-sangah]

Hi, I'm just starting with open source.
would it be okay if I take on this issue as the assignee?