Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.6.0-alpha2
    • Component/s: backend
    • Labels:
      None

      Description

      Context:
      In order to implement a role system on collections it is required to have basic CRUD operations for these.

      AT:

      • user/groups with assigned roles can be set on collections (called roleEntry)
      • one roleEntry is always a 1:1 mapping of one user or group to a role
      • the available roles are Viewer, Editor, Manager
      • there is a REST API to add/remove/edit a roleEntry
      • for a particular user or group there can only be one roleEntry per collection
        • on an attempt to add a roleEntry for an already existing identity (user/group) it is rejected with a conflict response
      • the last roleEntry of role type Manager cannot be deleted or updated, an attempt is rejected with a conflict response
      • the REST api is documented in the wiki

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              sebastian.bathke Sebastian Bathke
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: