#18998: Removing an authentication backend that's cached in a user's session
causes
exception
-------------------------------------+-------------------------------------
Reporter: Bradley Ayers | Owner:
<brad@…> | jorgebastida
Type: Bug | Status: assigned
Component: contrib.auth | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jorgebastida):
In the same way if a user logs in with backend A and then we remove A from
{{{AUTHENTICATION_BACKENDS}}} the user will still be log in even if the
backend is no longer available in {{{AUTHENTICATION_BACKENDS}}} but the
module is.
Will write a patch and send a Pull Request.
--
Ticket URL: <https://code.djangoproject.com/ticket/18998#comment:10>
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.
