#33522: Unexpected behaviour when logging in
-------------------------------------+-------------------------------------
Reporter: Michael | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 4.0
Severity: Normal | Resolution: invalid
Keywords: authentication log | Triage Stage:
in CSRF token | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Michael):
* status: new => closed
* resolution: => invalid
Comment:
It seems like pre-login session token, and creating a new session is
required for security due to my research, so this suggestion is invalid.
I think the solution is to create a custom CSRF view that if there is a
CSRF failure, you redirect the user to the page they want to see in the
first place, and it will now work cause they already logged in.
--
Ticket URL: <https://code.djangoproject.com/ticket/33522#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.eaac206ffb046da4e68a518479b8b90e%40djangoproject.com.
