search for: dupliation

> Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of the > other files in the same directory) directly, do all changes through > sam.ldb, otherwise you have a very good risk of further damaging your > database. I'm not sure if the dup keys in the 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' is my root issue and why the dbcheck fails with that

On Thu, 18 Jul 2024 10:29:04 +0200 Heiko Robert via samba <samba at lists.samba.org> wrote: > > Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of > > the other files in the same directory) directly, do all changes > > through sam.ldb, otherwise you have a very good risk of further > > damaging your database. > > I'm not sure if

Hello Timo, your patch introducing pass_attr_names and user_attr_names fixed the problem of the 'shared' attr_names member of [passdb|userdb]_ldap_conn as I answered in the relative thread. Now I think there is a problem while comparing user-provided and ldap-provided passwords causing a false 'password mismatch' situation, while using PLAIN mechanism with LDAP authentication.

> Anything after the 'Join failed' can be ignored, it is just an > artefact of the cleanup. > > I posted this: > > Do not remove the existing database, well not unless you want to > recreate your domain. > > I will amend it: > > Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of the > other files in the same directory)