-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User and ip lockout #40
Conversation
|
3 similar comments
2 similar comments
@mrbaboon thank you, I'll take a look at this PR shortly. |
LGTM @marcusmartins @shin- let me know if it looks good to you. |
LGTM |
The code LGTM but we should add some docs on usage and behavior. |
@marcusmartins I agree, oversight on my part. I'll add the docs in later today or tomorrow then we can close it out. |
Clean up inconsistent styles
Docs are added! |
2 similar comments
@@ -13,7 +13,7 @@ backend best fits their needs. | |||
Build status | |||
------------ | |||
|
|||
[![Build Status](https://travis-ci.org/kencochrane/django-defender.svg)](https://travis-ci.org/kencochrane/django-defender) [![Coverage Status](https://img.shields.io/coveralls/kencochrane/django-defender.svg)](https://coveralls.io/r/kencochrane/django-defender)[![Code Health](https://landscape.io/github/kencochrane/django-defender/master/landscape.svg)](https://landscape.io/github/kencochrane/django-defender/master) | |||
[![Build Status](https://travis-ci.org/mrbaboon/django-defender.svg)](https://travis-ci.org/mrbaboon/django-defender) [![Coverage Status](https://img.shields.io/coveralls/kencochrane/django-defender.svg)](https://coveralls.io/r/kencochrane/django-defender)[![Code Health](https://landscape.io/github/kencochrane/django-defender/master/landscape.svg)](https://landscape.io/github/kencochrane/django-defender/master) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably don't need to change to your status icon, keeping it kencochrane would be best so that it works on master.
Ah yes, sorry, missed that in my diff, good catch! |
THank you. |
Allow username and IP to be mutually exclusive when performing lockouts. This resolves an issue where you may have many users behind a single IP (common amongst our enterprise customers) where 1 user forgetting their password will lock out their peers.
The setting changes the lockout checks to evaluate if the IP failure limit and the username failure limit has been reached before issuing the lockout.
Any suggestions or comments are more than welcome!