#28285: Updating Password Hasher Invalidates Users First Login After Upgrade
---------------------------------+--------------------------------------
Reporter: Simon Blanchard | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by Simon Blanchard):
Replying to [comment:1 Tim Graham]:
> Here's my understanding of the scenario:
> 1. User X logs in and creates session A
> 2. Number of hash iterations changes in Django due to a software upgrade
> 3. Session A is still valid at this point
I don't think so. Hash changes invalidate the session. Hence the need for
the update_session_auth_hash() function
> 4. For whatever reason (using a different browser perhaps), user X logs
in and creates session B, triggering a password hash upgrade and an
invalidation of session A
>
I think the hash upgrade already happened in your point 2 above
--
Ticket URL: <https://code.djangoproject.com/ticket/28285#comment:2>
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/064.bcd0cee7b688af7cb35ae772107c6fee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
