#27027: force_login() now requires an authentication backend if multiple are
configured
-----------------------------------+--------------------------------------
     Reporter:  bendemboski        |                    Owner:  nobody
         Type:  Bug                |                   Status:  closed
    Component:  Testing framework  |                  Version:  1.10
     Severity:  Normal             |               Resolution:  fixed
     Keywords:                     |             Triage Stage:  Unreviewed
    Has patch:  1                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+--------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"d68b145a6f6e5e5dc1775cdaa904d83ee28ed615" d68b145]:
 {{{
 #!CommitTicketReference repository=""
 revision="d68b145a6f6e5e5dc1775cdaa904d83ee28ed615"
 [1.10.x] Fixed #27027 -- Restored Client.force_login() defaulting to the
 first auth backend.

 Backport of fc8f097117af7ada616fad20ae5b417fcf740413 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/27027#comment:3>
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/069.4f0a664003963e55d7efa1f8eb15ce41%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to