General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
820RequirementsRequirementNewHigh(Requirement) Common API for authentication and authorization operationsDave Vieglais2010-09-06 21:23Requirement
795RequirementsRequirementNewHigh(Requirement) System must support revocation of user permissionsDave Vieglais2010-08-29 20:45Requirement
777RequirementsRequirementNewHigh(Requirement) Authorization rules should support common permission levelsDave Vieglais2010-09-06 20:49Requirement
772RequirementsRequirementNewHigh(Requirement) Authentication services should be compatible with existing infrastructure and applicationsDave Vieglais2010-08-11 07:54Requirement
374RequirementsRequirementNewLow(Requirement) Periodic Reporting to Sponsor2010-03-16 18:11
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
371RequirementsRequirementNewLow(Requirement) Provide a suite of collaboration tools and instruction on how to use them2010-03-16 20:06
770RequirementsRequirementNewHigh(Requirement) Authorization system should be able to express the pseudo-principal concepts like 'public'Dave Vieglais2010-08-11 00:41Requirement
339RequirementsRequirementNewLow(Requirement) Web presence to provide publicly accessible information about the project2010-03-16 17:36
769RequirementsRequirementNewHigh(Requirement) Authorization should support critical roles, such as curators and system administratorsDave Vieglais2010-09-06 03:02Requirement
768RequirementsRequirementNewHigh(Requirement) Need default authz policies that resolve problems associated with inaccessible principalsDave Vieglais2010-08-11 00:34Requirement
580RequirementsRequirementNewLow(Requirement) All software developed on the project should be open sourceDave Vieglais2010-04-15 22:57
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
765RequirementsRequirementNewHigh(Requirement) Tools can access an API for authn and authzDave Vieglais2010-09-06 20:30Requirement
337RequirementsRequirementNewLow(Requirement) Deploy three coordinating nodes2010-03-17 15:14
764RequirementsRequirementNewHigh(Requirement) Authentication and access control should be consistently availableDave Vieglais2010-09-06 20:32Requirement
318RequirementsRequirementNewHigh(Requirement) Sponsor required Y1 functionalityDave Vieglais2010-09-06 03:24d1_common_java
763RequirementsRequirementNewHigh(Requirement) Authentication and authorization services are geographically replicatedDave Vieglais2010-09-06 20:52Requirement
392RequirementsRequirementNewHigh(Requirement) Identity and access control should be interoperable across datanetsDave Vieglais2010-09-06 20:31Requirement
393RequirementsRequirementNewHigh(Requirement) Access control rule evaluation must be highly scalable and responsive.Dave Vieglais2010-09-06 20:27Requirement
391RequirementsRequirementNewHigh(Requirement) Enable different classes of users commensurate with their roles.Dave Vieglais2010-09-06 20:51Requirement
390RequirementsRequirementNewHigh(Requirement) Consistent mechanism for identifying usersDave Vieglais2010-09-06 20:50Requirement
389RequirementsRequirementNewLow(Requirement) Implement a Member Node based on the ORNL DAAC2010-03-25 14:46
408RequirementsRequirementNewLow(Requirement) Implement a Coordinating Node software stack2010-03-25 15:44
(1076-1100/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)