No search after succesful bind.

[mrnours]

Hello,

I'm just trying to get the plugin to work on the last taiga version.
I had followed the guide to install it without docker.

The problem is that the server keeps saying that my password is incorrect with a valid ldap account.
But on the ldap server side i see that the authentification is succesful but there is no search operation afterward.

Any clues?

I had a taiga 5 server with an old version of this plugin that is working with the same ldap server...

Thanks for your help.

[dsalgueiror]

From what I have been able to test and the same thing happens to me in our installation migrated from Taiga 5 to 6 latest version, the authentication works well for Taiga but in the login process it updates or modifies the password value of the users table and this prevents the access to the Django admin because the encryption is different, expecting to have data of type pbkdf2_sha256$xxxxxxxxx. In the case of using the option to recover password and indicating it manually, the data saved in the DB is correct but once I log in again in Taiga it is modified.

I'm using the taiga-contrib-ldap-auth-ext plugin and it supposedly has an option to disable this behavior via LDAP_SAVE_LOGIN_PASSWORD = False, but it doesn't work. In addition to this being the case, I understand that the Django admin would not be using LDAP validation if not the one stored at that moment in the DB.

Greetings!!

[dsalgueiror]

Well, last discard test, I have finally commented #LDAP_SAVE_LOGIN_PASSWORD = False and working!!