Avoid mass acquistion when editing group gidNumber

Requirements

Descriptive title for this enhancement

Actual behavior

When a posix group is deleted or modified ( like modified the gidNumber or name ), Fd check consistency on all people which user the posixAccount feature. By checking consistency of all account and if SINAPS is enabled all account is scanned and corresponding acquisition is sent I see in log ldap request to get all attribute sent to sinaps

Jan 25 10:15:28 mc-pas-test slapd[698]: conn=17763 op=21987 SRCH attr=supannRefId supannEntiteAffectationPrincipale telephoneNumber facsimileTelephoneNumber mail mobi
le dn

for one modification I see 382 request

root@mc-pas-test:/var/cache/fusiondirectory/tmp# grep " SRCH attr=supannRefId supannEntiteAffectationPrincipale" /var/log/syslog |grep 17763 |wc -l
382

which is corresponding to posixuser concerned by the modified group

Expected behavior

Acquisition is sent only when field specified in fdSinapsAcquisitionContactMethodMap are modified

Step by step description of new behaviour

1. modify/delete a group
2. as this change didn't concern to sinaps information no acquisition should be launched

Benefits

group modification more quick

Possible Drawbacks

code complexity

additional information

It seems that modification launch other actions like mailbox check ( partage for example)

assigned to @MCMic

changed the description

added enhancement plugin-sinaps labels

added 5m of time spent at 2019-02-12

added PJ1807-0216 label

We can change sinapsUser to only start acquisition if synchronized fields are changed, but in this case we should add a checkbox field to force acquisition if needed.

changed milestone to %FusionDirectory 1.3.1

mentioned in commit ba4bd310

mentioned in commit e35586cc

changed title from SINAPS : avoid mass acquistion when add/remove group to Avoid mass acquistion when editing group gidNumber

added 1h 30m of time spent at 2019-03-07

added To Be Tested label

changed milestone to %FusionDirectory 1.3.2

hello @MCMic,

a prioiri bon aussi , les acquisitions ne sont envoyés qu'en cas de modif des champs mis dans le backend de config ( testé avec le champs description par exemple, mais pas avec le gidnumber)

changed milestone to %FusionDirectory 1.3.1

removed To Be Tested label