REVIEW-29: SDIACT-239 Update cilogon.org to support OAuth 2.0 - Test Readiness Review

CILogon provides XSEDE users certificates that they can use to authenticate to XSEDE SPs using their campus InCommon credentials. This is just another way of authenticating to XSEDE SPs and thus does NOT replace the standard authentication mechanisms that XSEDE users use. SDIACT-239 enhances the CILogon service to support the OAuth 2.0 protocol.

• (Shava) Old deployment plan format
  • Developer revised deployment plan using current template
• (Susan) Google links on CILogin doc page are invalid
  • Not yet fixed – needs to be fixed before end of testing
• (Susan) Following links in CILogon page sometimes opens up a new window and sometimes not – be consistent
  • Not yet fixed – needs to be fixed before end of testing
• (Shava) Prerequisites for Test Machine not specified
  • Developer added sudo requirement

Software (use the latest revision below)

• Already deployed to CILogon.org

Documentation

• Introduction
  • http://www.cilogon.org/faq#TOC-What-is-CILogon-2.0-
• Design/Security overview
  • Security and General Design Description
• Installation guide
  • n/a
• Deployment Plan
  • SDIACT-239 Deployment Plan
• User guide
  • Guide
• Defect, issue, and risk reporting
  • See SDIACT-239 test plan below
• Acceptance test plan
  • Test Plan
• Testing resources
  • hpcdev-pub04.sdsc.edu (CentOS 6 - Galen)
  • PSC node (CentOS 7 - Susan)

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.