Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
392RequirementsRequirementNewHigh(Requirement) Identity and access control should be interoperable across datanetsDave Vieglais2010-09-06 20:31Requirement
765RequirementsRequirementNewHigh(Requirement) Tools can access an API for authn and authzDave Vieglais2010-09-06 20:30Requirement
393RequirementsRequirementNewHigh(Requirement) Access control rule evaluation must be highly scalable and responsive.Dave Vieglais2010-09-06 20:27Requirement
771RequirementsRequirementNewHigh(Requirement) User identities should have simple string serializations that express both the user identity and namespace from which it is drawnDave Vieglais2010-09-06 03:12Requirement
761RequirementsRequirementNewHigh(Requirement) Users can specify authorization rules for data objects, science metadata objects, and process artifacts separatelyDave Vieglais2010-09-06 03:06Requirement
769RequirementsRequirementNewHigh(Requirement) Authorization should support critical roles, such as curators and system administratorsDave Vieglais2010-09-06 03:02Requirement
762RequirementsRequirementNewHigh(Requirement) User identities can be derived from existing institutional directory servicesDave Vieglais2010-09-06 03:01Requirement
795RequirementsRequirementNewHigh(Requirement) System must support revocation of user permissionsDave Vieglais2010-08-29 20:45Requirement
772RequirementsRequirementNewHigh(Requirement) Authentication services should be compatible with existing infrastructure and applicationsDave Vieglais2010-08-11 07:54Requirement
770RequirementsRequirementNewHigh(Requirement) Authorization system should be able to express the pseudo-principal concepts like 'public'Dave Vieglais2010-08-11 00:41Requirement
768RequirementsRequirementNewHigh(Requirement) Need default authz policies that resolve problems associated with inaccessible principalsDave Vieglais2010-08-11 00:34Requirement
767RequirementsRequirementNewHigh(Requirement) Users need to be able to express embargo rules for dataDave Vieglais2010-08-11 00:16Requirement
766RequirementsRequirementNewHigh(Requirement) Users should be able to easily assign proxy privileges to other users and to systems acting on their behalf for limited time durationsDave Vieglais2010-08-11 00:11Requirement
387RequirementsRequirementNewLow(Requirement) Implement a Member Node based on Metacat2010-10-06 22:00
632RequirementsRequirementNewLow(Requirement) Monitor the DataONE infrastructure2010-05-28 20:10
581RequirementsRequirementNewLow(Requirement) System supports multiple types of science metadata2010-04-20 20:45
580RequirementsRequirementNewLow(Requirement) All software developed on the project should be open sourceDave Vieglais2010-04-15 22:57
468RequirementsRequirementNewLow(Requirement) Design the cyberinfrastructure for the project.2010-03-25 16:51
408RequirementsRequirementNewLow(Requirement) Implement a Coordinating Node software stack2010-03-25 15:44
410RequirementsRequirementNewLow(Requirement) The infrastructure must support long term preservation of Data2010-03-25 15:41
412RequirementsRequirementNewLow(Requirement) Identifiers always refer to the same object2010-03-25 15:41
389RequirementsRequirementNewLow(Requirement) Implement a Member Node based on the ORNL DAAC2010-03-25 14:46
431RequirementsRequirementNewLow(Requirement) Software developed for infrastructure should be implemented according to specifications2010-03-25 14:44
409RequirementsRequirementNewLow(Requirement) Develop a reference implementation of the Member Node stack2010-03-25 13:57
455RequirementsRequirementNewLow(Requirement) Installation of critical software must be well documented and as automated as possible2010-03-25 13:52
(51-75/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)