GRP-14: Use a group to control access within an application

Executive Summary: 
A community member needs to use a community group to control access within an application. Notable reasons include: a campus or L3 service offers services to specific community members, a science gateway offers group-based access control to gateway functions or resources, a project member limits access to a project tool (or administrative privilege within a project tool) to members of a project’s WBS group.
User Importance Summary: 
Community members need to be able to define arbitrary groups of people to which they can refer for authorization and communication purposes. Researchers need these groups to be visible/usable within applications, science gateways, and campus IT systems (in a campus bridging scenario).
Target Communities and Sizes: 
Science gateway and application developers - 100 < N < 1,000 Campus IT administrators involved in campus bridging - 100 < N < 1,000 Independent resource providers - 100 < N < 1,000
Documents:
Full description (public)
Full description (for review)
Full description (drafting version)
Capability delivery plan
Status: 
Approved
Priority: 
LOW (2018-01)
Use Case Author: 
Lee Liming
Use Case End User: 
independent resource provider
application developer
science gateway developers
campus IT administrator
Area: 
Account Management
Sub-Area: 
Group Management
First Proposed Date: 
2017-05-01
Last Approved Date: 
2019-08-01

National Science Foundation (NSF)

© ACCESS All Rights Reserved.

ACCESS is an advanced computing and data resource supported by the National Science Foundation and made possible through these lead institutions and their partners:
Carnegie Mellon University, University of Colorado Boulder, University of Illinois at Urbana-Champaign, and State University of New York at Buffalo .


Administrative Login