Uploaded image for project: 'Syncope'
  1. Syncope
  2. SYNCOPE-1062

Changes pulled from one resource not propagated externally

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.2
    • Fix Version/s: 2.0.3, 2.1.0
    • Component/s: core
    • Labels:
      None

      Description

      Let's suppose to have:

      1. resource R1 supporting user propagation
      2. group G with resource R1 assigned
      3. resource R2 supporting user pull
      4. pull task T for R2, with user template set for granting G membership

      When executing T the first time, user U is created internally and propagated to R1, as expected.

      If U is modified on R2 (attribute change), when T is executed again the expected change is reflected on U internally. Nothing is changed, however, on R1.

      If U is modified on R2 again and T executed the third time, the expected change is still reflected on U internally. R1, however, receives the change coming from the former T execution.

        Attachments

          Activity

            People

            • Assignee:
              ilgrosso Francesco Chicchiriccò
              Reporter:
              ilgrosso Francesco Chicchiriccò
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: