Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-19089

Deletion of Permission target fail in Access Federation

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 6.9.0
    • Fix Version/s: None
    • Labels:
      None

      Description

       

      Access federation (Full Mesh topology)  was enabled between 3 instances A, B and C with Artifactory version 6.9.0.

      1. In A, maven-test-starling-release (permission target ) was created with local (maven-test-starling-release-local).
      2. Previously, Security plugin was synchronizing permissions between instance A and B
      3. Seeding of data was performed for C from A using REST API calls.
      4. Access federation was setup between A, B and C.
      5. A permission target was removed from A and the local repo manually in A.
      6. A and B does not have the permission target:maven-test-starling-release, local repo.
      7. But C still shows the permission target maven-test-starling-release but no association with the local repo.
      8. Under Repos in Artifactory C shows the local repo (maven-adobe-starling-aem61-release-local) in it.

      We couldn't reproduce the issue in test env. Logs: https://supportlogs.jfrog.com/logs/102819/

      Please let us know why access federation is not able to propagate the deletion to all the federated instances ?

        Attachments

          Activity

            People

            Assignee:
            ofira Ofir Azoulay-Rozanes
            Reporter:
            sowjanyak Sowjanya Kamatam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: