Add Groups Object models

[eaquigley]

---

Author Name: Michael Bar-Sinai (@michbarsinai)
Original Redmine Issue: 3500, https://redmine.hmdc.harvard.edu/issues/3500
Original Date: 2014-02-03
Original Assignee: Michael Bar-Sinai

---

Groups are sets of users defined per dataverse. Groups can get roles and are inherited the same way permissions are.

---

Related issue(s): #700
Redmine related issue(s): 4156

---

[eaquigley]

---

Original Redmine Comment
Author Name: Gustavo Durand (@scolapasta)
Original Date: 2014-03-10T22:41:09Z

---

Not really sure what happened with this ticket, but it got moved around a bunch. Michael, can you review?

When done it should go to QA and they will test and mark as completed (or pass back to you).

[eaquigley]

---

Original Redmine Comment
Author Name: Michael Bar-Sinai (@michbarsinai)
Original Date: 2014-03-18T17:54:08Z

---

Discussion of features underway in at
https://docs.google.com/document/d/1P4HOUuJEoPfU06-4R9xP0nRFapNyZUg5xnjYNVRvFik/edit

[michbarsinai]

Groups are added (back-end and API, including docs). Below is a printout of a very simple test.

# Sample test script
# Assumes this runs from the API folder, dv13 exists, and we have ADMIN_KEY for the API key of admin,
# and GABBI_KEY for the API key of Gabbi Guest.

# Make an explicit group (EG-1) on dv 13 
curl -X POST -d@data/explicit-group-first.json -H"Content-type:application/json" http://localhost:8080/api/dvs/13/groups?key=$ADMIN_KEY
# returns {"status":"OK","data":{"identifier":"&explicit/13-EG-1","groupAliasInOwner":"EG-1","owner":13,"description":"This is the description field","displayName":"Explicit Group number one","containedRoleAssignees":[]}}

# Now add Gabbi to the group
curl -X PUT http://localhost:8080/api/dvs/13/groups/EG-1/roleAssignees/@gabbi?key=$ADMIN_KEY
# returns {"status":"OK","data":{"identifier":"&explicit/13-EG-1","groupAliasInOwner":"EG-1","owner":13,"description":"This is the description field","displayName":"Explicit Group number one","containedRoleAssignees":["@gabbi"]}}

# Test Gabbi's permissions:
curl http://localhost:8080/api/test/permissions/13?key=$GABBI_KEY
# Returns {"status":"OK","data":[]}

# Assign a role to the explicit group. Note that the group global identifier is &explicit/13-EG-1.
curl -X POST -d \{\"assignee\":\"\&explicit/13-EG-1\",\"role\":\"curator\"\} -H "Content-type:application/json" http://localhost:8080/api/dvs/13/assignments/?key=$ADMIN_KEY
# returns {"status":"OK","data":{"id":29,"assignee":"&explicit/13-EG-1","roleId":8,"_roleAlias":"curator","definitionPointId":13}}

# test Gabbi's permissions again:
curl http://localhost:8080/api/test/permissions/13?key=$GABBI_KEY
# returns {"status":"OK","data":["AddDataverse","AddDataset","ViewUnpublishedDataverse","ViewUnpublishedDataset","DownloadFile","EditDataset","ManageDataversePermissions","PublishDataverse","DeleteDataverse"]}

# Gabbi got permissions via the group. PASS.

[kcondon]

The above test works so I am assuming the scope of this ticket is the creation and assigning of groups/perms, not necessarily the enforcing of terms in the app. I added that issue to #1380.

I did find that the test api functions do not accept both dv db id and dv alias for arguments though the general api commands do.

Closing