Project

General

Profile

Feature #7023

Treat CHANGEPERMISSION the same as ALL

Added by ben leinfelder over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
metacat
Target version:
Start date:
05/11/2016
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

To better conform with the DataONE access control model, we are going to treat the change permission the same as all in the Metacat API. Currently, the three permissions are handled independently and do not cascade like they do in DataONE.
With this change, higher permissions will implicitly allow lower (write implies read; changepermission implies write and read; all will still mean all three)

History

#1 Updated by ben leinfelder over 4 years ago

  • Status changed from New to In Progress

I've updated the 2.6 branch code to reflect this more relaxed interpretation of ACLs. I've also modified the access control tests to treat the permissions as cascading.

#2 Updated by ben leinfelder over 4 years ago

  • Status changed from In Progress to Closed

All tests have been updated to reflect cascading permissions

Also available in: Atom PDF