Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-2745

Always Create (paths for) ACLs, and expose in link headers

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Fedora 5.0.0
    • Fix Version/s: Fedora 5.0.0
    • Component/s: auth
    • Labels:
    • Roadmap Theme:
      Services: Authorization
    • Epic Link:
    • Sprint:
      Fedora 2018 API Alignment 02

      Description

      Section 5.3 of the Fedora spec states:
      "A conforming server MUST advertise the individual resource ACL for every controlled resource in HTTP responses with a rel="acl" link in the Link header, whether or not the ACL exists."

      So Fedora needs to always advertise an ACL location the client can PUT to to create an ACL, even if it doesn't exist already.

      https://fcrepo.github.io/fcrepo-specification/#link-rel-acl

       

      Peter Eichman's proposed the path:  /resource/fcr:acl

       

      As documented in a related, overlapping, and now closed ticket ( https://jira.duraspace.org/browse/FCREPO-2744 )  this ticket will entail removing the use of acl:accessControl in order to create the rel=acl header link.

      To complete the issue, 

      1. Every resource with the exception of all resource's ending in /fcr:acl should return a link header as follows:  Link: <resource-uri/fcr:acl>; rel="acl"
      2. The old way of doing things (populating the rel="acl" using the <> acl:accessControl <aclpath>  statement),  acl validation , and support for specifying an ACL on resource creation, should be removed.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lsitu Longshou Situ
              Reporter:
              birkland Aaron Birkland
              Reviewer:
              Jared Whiklo
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: