The lastSync mechanism was designed to help guarantee that effective assignment calculations are propagated to the target system in the event that a target system was down for some reason. The lastSync stores the last SUCCESSFULLY sync'd effective assignment to a target system.
Currently we only support this mechanism on managed user objects that are maintained via the explicit 'managed/user' resource path. If you have a user object, even managed user objects, that are not tied to the managed/user path this mechanism will not work.
Improvements to investigate :
- Storing the last sync mechanism on the link instead
- Store lastSync in a separate object that can be managed via a relationship
- Allow the last sync mechanism to work on any managed object that uses the effectiveAssignments attribute
- Queued sync can potentially avoid this if the retry is set up accordingly - not supported out of the box but can be positioned so
- Move to Java
Related BUGS why lastSync was introduced :