#18998: Removing an authentication backend that's cached in a user's session
causes
exception
-------------------------------------+-------------------------------------
Reporter: Bradley Ayers | Owner:
<brad@…> | jorgebastida
Type: Bug | Status: closed
Component: contrib.auth | Version: 1.4
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 1 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"dc43fbc2f21c12e34e309d0e8a121020391aa03a"]:
{{{
#!CommitTicketReference repository=""
revision="dc43fbc2f21c12e34e309d0e8a121020391aa03a"
Fixed #18998 - Prevented session crash when auth backend removed
Removing a backend configured in AUTHENTICATION_BACKENDS should not
raise an exception for existing sessions, but should make already
logged-in users disconnect.
Thanks Bradley Ayers for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18998#comment:12>
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].
For more options, visit https://groups.google.com/groups/opt_out.
