#20495: add login failure events to django.security logger
------------------------------------------------+------------------------
Reporter: ptone | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
#18616 added a signal for failed login attempts - a primary use-case for
this was monitoring.
With #19866 we have the introduction of a django.security logger, and it
would make more sense to log these events there.
I'd be +0 on also deprecating the signal, they are brand new, and probably
don't have much traction. There may be non-monitoring uses of said signal
though that I'm not thinking of.
--
Ticket URL: <https://code.djangoproject.com/ticket/20495>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.adae1b801b9ffc0e17165f33d8d41f56%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
