it contrats at evam ch wrote:
> we use a null service driver to calculate and fill a custom attribute
> when the groupmembership of a user change.
> The trouble is that the changes in nested group is not detected by the
> driver, and our rule aren't run.
> I try the "Revert to calculated membership value behavior" option, but
> no succes.
This setting onyl affects reading group memberships off a group/user from
policy. It does not trigger event creation from nested memberships as you
already found out.
> What can i do to make this work right?
You ned to move from an event triggered to a scheduled sync appriach, e.g. add
atrigger job to your null driver that produces one trigger operation per
group/user you need to update and check their members/memberships from policy.
To detect membership changes you could assign the group's member attribute to a
nodeset variable, serialize it as XML, then calculate a hash value. Store it on
the group object and compare subsequent runs against the stored value: if it is
different, update your cutom attribute.