Hi,

I suspect that PasswordPolicy is responsible for this beahaviour. Each time some user binds on the server, the entry will be updated, thus generating a new entryCSN. (I have to double check that).

In any case, the previous entryCSN should get removed.

I'll check the code.


On 20/12/2019 15:54, Jörg Andreas (Galexis) wrote:
Yes we have PasswordPolicy set. I’ll send you the file to 
elech…[email protected]<http://gmai.com>.

Andreas


Am 20.12.2019 um 15:26 schrieb Emmanuel Lécharny 
<[email protected]<mailto:[email protected]>>:


On 20/12/2019 14:31, Jörg Andreas (Galexis) wrote:
Hi Emmanuel

Thanks for the fast reply. We have no replication enabled and no replication 
consumer configured. I can send you our current configuration file. We also 
checked, that journaling is disabled, but that would be a different file anyway.


Yes, please, send the configuration file.


Maybe there is a flag we missed?

hmmm, I don't see which one could cause such a behavior. This index is not 
supposed to move as soon as the entry has been created, unless it's updated.


May be you have PasswordPolicy set ?



---------------------------------------------------------------------
To unsubscribe, e-mail: 
[email protected]<mailto:[email protected]>
For additional commands, e-mail: 
[email protected]<mailto:[email protected]>



This message may contain confidential information and is intended only for the 
individual named herein. If you are not the herein named addressee you should 
not disseminate, distribute, copy or otherwise make use of this e-mail. Please 
notify the sender immediately by e-mail if you have received this e-mail by 
mistake, and delete this e-mail from your system. Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to