Allow for association with session user

[tacerus]

1. Allow for association with session user

   In environments with multiple authentication backends it can be
   desirable to link an LDAP login with an existing user.

2. Allow sync relation function to return user

   If existing users are associated, it can be useful to similarly compare
   an LDAP login with a model containing users created through different
   backends, and further to use a found user object instead of creating a
   new one.

[etianen]

Thanks for this!

I'm a bit confused about the use-case, however! I've implemented apps with multiple authentication backends before, and this package works with no further modification. Indeed, it's quite possible to have a User record with a working password to support the built-in ModelBackend, and also have that record associated with the LDAP backend.

I'm confused as to how request.user would be populated without using AuthenticationMiddleware. Is this to integrate with RemoteUserMiddleware or some other 3rd-party auth-style middleware?

[tacerus]

Thanks for the input, I'm unfortunately slightly confused too, I am using django.contrib.auth.middleware.AuthenticationMiddleware in my application. It uses both social_core and django_python3_ldap backends. Without this patch, a user could only log in with LDAP (initiating their authenticated session) and afterwards (in the same session) with Social to keep a "relation" and the same Django user. With this patch, it additionally works if the user first logs in with Social and then with LDAP. Am I missing something (either in how I would make this work without the patch or in the question)?