Uploaded image for project: 'Islandora'
  1. Islandora
  2. ISLANDORA-1183

XACML relations not being set correctly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Ready for Test
    • Affects Version/s: 7.x-1.3, 7.x-1.4
    • Fix Version/s: 7.x-1.5
    • Component/s: XACML Editor
    • Labels:
      None

      Description

      Due to a disconnect between how users and roles are acquired for writing POLICY datastreams and the entries reflecting them in the RELS-EXT(/-INT), it was possible for the set of relationships written to be a subset of those written to the POLICY.

      This issue would be likely to manifest as objects with XACML viewing restrictions showing up in lists of results of users/roles who do not have access to view them, and so getting 403s(/404s?) when trying to access them.

      This issue should only affect POLICY streams written with the XACML API directly--those written with the "editor" UI should be fine, due to validation the editor performs (requiring the user enabling the viewing rule to be selected)... This issue may potentially affect POLICY streams written with the "Scholar Embargo" module.

      https://github.com/Islandora/islandora_xacml_editor/pull/109
      A pull with an update hook still to come.

        Attachments

          Activity

            People

            • Assignee:
              kimpham54 Kim Pham
              Reporter:
              willtp87 William Panting
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: