Closed lethal1986 closed 2 weeks ago
Hello,
Was the modifyTimestamp
attribute updated when you restored user t1u2
? Maybe you need to manually update it on OpenLDAP side?
Hello Nicolas,
Thanks for the hint. You were right, in OpanLDAP the modifyTimestamp attribute does not changed for user "t1us2" in this case. Therefore the differential sync does not synch this user.
In alfresco-content-repository-community:23.3.0 (and also in enterprise version) with LDAP differential sync we are facing a strange phenomenon.
It seems that differential synchronisation does not puts back a user to a group, if the user was previously removed and after that restored in AD.
In order to detail the problem we set up an OpenLDAP server and configure Alfresco to use this OpenLdap server ldap-authentication.properties settings.
Here are the steps we have done:
synchronizer.synchronize(true, true);
Here is the same log for enterprise version, with the same output: alfresco_enterprise.log
Additional note: It seems that the phenomenon happens, if the user has to created by Alfresco due to the differential sync.
Expected behaviour: In case of differential sync users and group membership also synchronised.