Call for Community Testing: 3.9.3 CAS
- What is a "Call for Community Testing"?
- Participating in the CAS testing call
- About CAS
- Reasons for testing CAS
- Technology dependencies
- Environment/build parameters and other special conditions to test
- Release notes
What is a "Call for Community Testing"?
A Call for Community Testing is a mechanism to notify our users that new Globus code is available for testing in the field. Through these calls, the Globus Alliance hopes to expose its code to a wide variety of usage scenarios early in its development process. The ultimate goals are to catch bugs that have historically been found only after final releases, and to elicit feedback from the community on ways our software can be improved.
Participating in the CAS Testing Call is easy!
- Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
- Install the software in a non-production environment. Use the 3.9.3 distribution from http://www-unix.globus.org/toolkit/downloads/development/; the code can also be retrieved directly from CVS using the tag [tag].
- Exercise the software.
- Log your experiences in http://bugzilla.globus.org/globus/ under the "[component]" product. Please mention 3.9.3 explicitly in the body of the report.
- Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
- If you have any questions are comments about the process, send an email to testing@globus.org.
Testing period
The testing period for this call is [date range].
About CAS
CAS allows a virtual organization to express policy regarding resources distributed across a number of sites. A CAS server issues assertions to the virtual organization users, granting them fine-grained access rights to resources. Servers recognize and enforce the assertions. CAS is designed to be extensible to multiple services and is currently supported by the GridFTP server.
Reasons for testing CAS
[describe why volunteers are needed]
Technology dependencies
The CAS service depends on the following GT components:
- WS Authentication and Authorization
- Java WS Core
The CAS GridFTP authorization module depends on the following GT components:
- Pre-WS Authentication and Authorization
The CAS service depends on the following 3rd party software:
- OpenSAML
The CAS GridFTP authorization module depends on the following 3rd party software:
- libxml
Environment/build parameters and other special conditions to test
- Use of various JVMs
- Administrative interface for granting/revoking rights
- Query interface, specifically assertion generation
- Various client tools.
Release notes
Release notes for the 3.9.3 CAS can be found here.