User is not synchronised when group membership is read from the group object
Group membership can be obtain by :
1 - reading an attribute in the user object (for example member can indicate the group's dn)
2 - reading an attribute in the group object (for example memberOf can indicate the user's dn)
When the group membership is filled in the user object, each membership changes update the user object, and then changes its ldap timestamp
but when the group membership is filled in the group object, it doesn't changes the user ldap timestamp, and user is not considered as to update (which means that the rules engine is not called)
MoYo : I understand the purpose but not the last parenthesis (which means that the rules engine is not called). Why speaking about RuleEngine ? User is not considered as to update... That's all, no ? RuleEngine is a simple consequence ?TODO :
- Based on glpi_users_groups is_dynamic fields, get groups linked to users and modifytimestamp (manage a cache for that). Update user timestamp to max group timestamp if > user timestamp.