Goal: Provide rationale for why the researcher, project and campus should pursue Assurance Certification to support Research
Possible collaborators: Jim Basney, Von Welch, Scott Koranda, Alan Sill, Tom Barton
Resources:
A Roadmap for Using NSF Cyberinfrastructure with inCommon
Scoping
- How much fed idm background do we need? Assurance has similar arguments.
Other
- ECP and Assurance?
Readers: Must be familiar with InCommon and Assurance (for now). Link to A Roadmap for Using NSF Cyberinfrastructure with inCommon for background on Research and federated identity.
Some view multiple credentials and managing all the certificates for access as part of a researchers job. It doesn't have to be.
Story (Ken's Jean Blue Story)
We help researchers spend more time on their research time and less time on IT.
Allow researchers to more easily collaborate and coordinate multiple resources through a single identity system rather than spending effort on managing multiple identities.
Allow NSF CI projects to leverage InCommon saving effort spent on establishing their own identity systems.
Utilization of federated identity for CI will bring uniformity to the authentication mechanism for science in line with the business processes of doing science.
Allow campuses and other institutions to provide their researchers with a consistent identity system for local research and administrative computing, and remote research computing.
FICAM approved TFP for REsearch and Education
Agency members
Collaborator members
InCommon Part of NSF's Roadmap; Assurance PRogram only one enabled in the Federation.