Task #6858
Feature #6498: V2 Metacat MN and CN Support
Access control on MN.updateSystemMetadata and CN.updateSystemMetadata
Start date:
2015-02-19
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
Who are allowed to call the two methods? Should CN and MN be same? Should CN.updateSystemMetadata and CN.changeAccessPolicy be same?
History
#1 Updated by Jing Tao about 9 years ago
- Assignee set to Jing Tao
#2 Updated by Jing Tao about 9 years ago
For MN.updateSystemMetadata, those client has the permission:
- Owner of object
- Authoritative Member Node
- Coordinating Node (no, because MN is authoritative)
- user subjects with the change permission
#3 Updated by Jing Tao about 9 years ago
- Subject changed from Access control on MN.updateSystemMetadata and CN.updateSystemMetadata to Access control on MN.updateSystemMetadata and CN.synchronizeObjects
For CN.syncrhonizeObjects, only the authoritative MN can call it.
#4 Updated by Jing Tao almost 9 years ago
- Subject changed from Access control on MN.updateSystemMetadata and CN.synchronizeObjects to Access control on MN.updateSystemMetadata and CN.updateSystemMetadata
Only CN can call CN.updateSystemMetadata.
#5 Updated by Jing Tao almost 9 years ago
- Status changed from New to Closed
- translation missing: en.field_remaining_hours set to 0.0
- % Done changed from 0 to 100
The above rules were implemented in MNodeService and CNodeService.
