Opened 11 years ago
Last modified 5 months ago
#21289 assigned New feature
Add login rate limiting to contrib.auth
Reported by: | Tim Graham | Owned by: | Tom Carrick |
---|---|---|---|
Component: | contrib.auth | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | sasha@…, ivanov17, Ülgen Sarıkavak | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | |||
Description ¶
This would need a design proposal. There are likely some third-party packages that provide this that we could borrow from or consider including in contrib.auth.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (9)
comment:1 by , 9 years ago
comment:3 by , 9 years ago
Cc: | added |
---|
comment:4 by , 3 years ago
#33743 was a duplicate suggesting to "Add topic page on rate-limiting solutions for Django to the documentation" in order to progress this ticket, as it doesn't look like a consensus on a solution in core is near.
comment:6 by , 13 months ago
I think this is still relevant, it would be great to have such functionality out of the box.
comment:7 by , 13 months ago
Cc: | added |
---|
comment:8 by , 11 months ago
Cc: | added |
---|
comment:9 by , 5 months ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Is the ticket still relevant? Considering availability of ready-made solutions for the framework, like
django-ratelimit
etc.