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

          sebastian.bathke Sebastian Bathke created issue -
          sebastian.bathke Sebastian Bathke made changes -
          Field Original Value New Value
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - Collections contain a set of user/groups with assigned roles
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Summary Add Permission/Role layer to collections Add Permission/Role-Management to collections
          sebastian.bathke Sebastian Bathke made changes -
          Summary Add Permission/Role-Management to collections Add Permission/Role-Management to Collections
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - the available roles are {Viewer, Editor, Manager}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - the available roles are {Viewer, Editor, Manager}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Labels current_release
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Status Open [ 1 ] In Specification [ 10000 ]
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - the last manager cannot be deleted
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Status In Specification [ 10000 ] In Development [ 10312 ]
          sebastian.bathke Sebastian Bathke made changes -
          Summary Add Permission/Role-Management to Collections Add Role-Management to Collections
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - the last manager cannot be deleted
          - there is a REST API to add/remove/edit a user/group role entry
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the last manager cannot be deleted
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Link This issue is related to OPT-2546 [ OPT-2546 ]
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - the last manager cannot be deleted
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - on an attempt to add a role for an already existing identity (user/group) it is rejected with a conflict response
          - the last manager cannot be deleted
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities for these.

          AT:
          - user/groups with assigned roles can be set on collections
          - one role entry is always a 1:1 mapping of one user or group to a role
          - for a particular user or group there can only be one entry in the role set (so there is only a 1:1 mapping of a particular user/group and role)
          - the available roles are {{Viewer, Editor, Manager}}
          - there is a REST API to add/remove/edit a user/group role entry
          - on an attempt to add a role for an already existing identity (user/group) it is rejected with a conflict response
          - the last manager cannot be deleted
          - the REST api is documented in the wiki
          Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities 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 (so there is only a 1:1 mapping of a particular user/group and role 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, an attempt is rejected with a conflict response
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          Status In Development [ 10312 ] In Review [ 10212 ]
          sebastian.bathke Sebastian Bathke made changes -
          Description Context:
          In order to implement a role/permission system based on collections it is required to have basic CRUD abilities 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 (so there is only a 1:1 mapping of a particular user/group and role 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, an attempt is rejected with a conflict response
          - the REST api is documented in the wiki
          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 (so there is only a 1:1 mapping of a particular user/group and role 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, an attempt is rejected with a conflict response
          - the REST api is documented in the wiki
          sebastian.bathke Sebastian Bathke made changes -
          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 (so there is only a 1:1 mapping of a particular user/group and role 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, an attempt is rejected with a conflict response
          - the REST api is documented in the wiki
          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 (so there is only a 1:1 mapping of a particular user/group and role 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
          sebastian.bathke Sebastian Bathke made changes -
          Assignee Sebastian Bathke [ sebastian.bathke ] Michael Wagner [ michael.wagner ]
          sebastian.bathke Sebastian Bathke made changes -
          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 (so there is only a 1:1 mapping of a particular user/group and role 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
          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
          michael.wagner Michael Wagner made changes -
          Assignee Michael Wagner [ michael.wagner ]
          Status In Review [ 10212 ] Done [ 10010 ]
          Resolution Done [ 10000 ]
          omran.abazeed Omran Abazeed made changes -
          Fix Version/s 2.6.0-alpha2 [ 15515 ]
          omran.abazeed Omran Abazeed made changes -
          Labels current_release

            People

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

              Dates

              • Created:
                Updated:
                Resolved: