Do you have deprecation warnings with Django 2.0.x? 
https://docs.djangoproject.com/en/dev/howto/upgrade-version/#resolving-deprecation-warnings

>From the 2.1 release notes: "The authenticate() method of authentication 
backends requires request as the first positional argument."

>From the 1.11 release notes: "authenticate() now passes a request argument 
to the authenticate() method of authentication backends. Support for 
methods that don’t accept request as the first positional argument will be 
removed in Django 2.1."

On Thursday, July 19, 2018 at 7:08:39 AM UTC-4, DirkBo wrote:
>
> After updating from 2.0.7 to 2.1rc1 when i 
> call django.contrib.auth.authenticate(), my custom authentication Backends 
> are now completely ignored, only django.contrib.auth.backends.ModelBackend 
> is used.
>
> Is this happening for someone else or did i miss some changes? 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/8136222c-d6a1-420a-b49d-5405ab67f977%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to