#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 | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by boylea):
Thank you for the wonderful feedback. So it seems that including both
logging the failed attempt, and signalling it, is the way to go here. If
this feature is to be removed, then that can be another ticket. So I will
include that change, and fix the use of the logger as suggested. For the
release docs, should I just append a section to the latest (1.6.txt)
release doc file, or put it under a bullet under the minor features title
(or does this matter much)?
--
Ticket URL: <https://code.djangoproject.com/ticket/20495#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.7604fc1290499c7ca8ec5c9db5f795c7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
