Produits Entr'ouvert » Authentic 2

LDAP passwords have to be kept around for two reasons:

• some LDAP attributes could be only readable by the User and not the identity which Authentic use to bind to the LDAP with the user credentials (service user),
• user's passwords are usually only modifiable by the user himself.

Currently the password is stored after successful authentication using the Django cache framework using a cache named 'ldap' if it exists and otherwise the default cache. They must use a shared cache (file, SQL, memcache but not locmem, the default). As the cache subsystem is not usually configured like that it makes using LDAP more difficult than necessary.

The provided patch add a middleware to keep the request around in a thread local variable and use it from the LDAPUser subclass of Django's User to retrieve the request session and store LDAP credentials. As session are always stored in a shared cache (default is SQL) it resolves the described problem of initial configuration by not needing it anymore.