REVIEW-42: XCI-30 Provide InCommon Identity Provider for XSEDE Identities - Test Readiness Review

Today a significant proportion of US researchers are unable to access services using a federated identity because their home institution does not operate a suitable InCommon identity provider (IdP). XSEDE users currently reside at over 500 US higher education institutions, while fewer than 130 institutions operate "research and scholarship” compatible InCommon IdPs (https://spaces.internet2.edu/x/-IKVAQ). As a result, XSEDE users have difficulty accessing federated services (e.g., GENI, LIGO, and other international science projects).

To address this need, XSEDE should operate an InCommon IdP for XSEDE users, allowing them to authenticate with their XSEDE Kerberos/Duo credentials for access to services federated by InCommon.

No comments provided – all materials looked good as is.

Documentation

• Introduction
  • https://www.xsede.org/security/incommon
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a
• Deployment Plan
  • XCI-30 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See XCI-30 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • portal.xsede.org and cilogon.org

Package information: All software packages (e.g., server and client packages) for this CI are listed.

Documentation and Installation instructions: The deployment plan for this CI on XSEDE is clearly described as well as the installation instructions and any XSEDE specific configuration instructions.

Test environment and facilities: The test environment needed to adequately to validate this component is described. Should indicate also whether testing can be performed within a VM and if not, the reasons for it.

Assumptions: Lists any assumptions needed before testing can begin (e.g., accounts needed).

Test procedures, cases, and scenarios: Lists the tests that should be run or an associated test suite and expected performance metrics if applicable.

Defect, issue, and risk reporting: Deployment plans should include defect and issue reporting information. The testing plan could reference that same information from the deployment plan, or provide alternate information if defects and issues need to be reported differently during testing. Risks, as well as defects and issues, should be part of the testing report.