Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-15729

LastSync functionality is tightly coupled to the managed/user resource path

    XMLWordPrintable

    Details

    • Bug
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • 7.1.0
    • None
    • None

      Description

      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 :

        Attachments

          Issue Links

            Activity

              People

              Unassigned Unassigned
              alin Alin Brici
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated: