General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
761RequirementsRequirementNewHigh(Requirement) Users can specify authorization rules for data objects, science metadata objects, and process artifacts separatelyDave Vieglais2010-09-06 03:06Requirement
764RequirementsRequirementNewHigh(Requirement) Authentication and access control should be consistently availableDave Vieglais2010-09-06 20:32Requirement
763RequirementsRequirementNewHigh(Requirement) Authentication and authorization services are geographically replicatedDave Vieglais2010-09-06 20:52Requirement
391RequirementsRequirementNewHigh(Requirement) Enable different classes of users commensurate with their roles.Dave Vieglais2010-09-06 20:51Requirement
769RequirementsRequirementNewHigh(Requirement) Authorization should support critical roles, such as curators and system administratorsDave Vieglais2010-09-06 03:02Requirement
770RequirementsRequirementNewHigh(Requirement) Authorization system should be able to express the pseudo-principal concepts like 'public'Dave Vieglais2010-08-11 00:41Requirement
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
392RequirementsRequirementNewHigh(Requirement) Identity and access control should be interoperable across datanetsDave Vieglais2010-09-06 20:31Requirement
768RequirementsRequirementNewHigh(Requirement) Need default authz policies that resolve problems associated with inaccessible principalsDave Vieglais2010-08-11 00:34Requirement
772RequirementsRequirementNewHigh(Requirement) Authentication services should be compatible with existing infrastructure and applicationsDave Vieglais2010-08-11 07:54Requirement
777RequirementsRequirementNewHigh(Requirement) Authorization rules should support common permission levelsDave Vieglais2010-09-06 20:49Requirement
820RequirementsRequirementNewHigh(Requirement) Common API for authentication and authorization operationsDave Vieglais2010-09-06 21:23Requirement
767RequirementsRequirementNewHigh(Requirement) Users need to be able to express embargo rules for dataDave Vieglais2010-08-11 00:16Requirement
765RequirementsRequirementNewHigh(Requirement) Tools can access an API for authn and authzDave Vieglais2010-09-06 20:30Requirement
390RequirementsRequirementNewHigh(Requirement) Consistent mechanism for identifying usersDave Vieglais2010-09-06 20:50Requirement
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
795RequirementsRequirementNewHigh(Requirement) System must support revocation of user permissionsDave Vieglais2010-08-29 20:45Requirement
762RequirementsRequirementNewHigh(Requirement) User identities can be derived from existing institutional directory servicesDave Vieglais2010-09-06 03:01Requirement
337RequirementsRequirementNewLow(Requirement) Deploy three coordinating nodes2010-03-17 15:14
389RequirementsRequirementNewLow(Requirement) Implement a Member Node based on the ORNL DAAC2010-03-25 14:46
388RequirementsRequirementNewLow(Requirement) Implement a Member Node based on Dryad2010-03-24 13:36
387RequirementsRequirementNewLow(Requirement) Implement a Member Node based on Metacat2010-10-06 22:00
386RequirementsRequirementNewLow(Requirement) Deploy at least three Member Nodes2010-03-17 13:39
385RequirementsRequirementNewLow(Requirement) Support arbitrary unique identifiers2010-03-16 22:09
632RequirementsRequirementNewLow(Requirement) Monitor the DataONE infrastructure2010-05-28 20:10
(1076-1100/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)