Call for Community Testing: 3.9.3 Delegation Service

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 Delegation Service Testing Call is easy!

  1. Optional: Consider sending mail to testing@globus.org to let us know that you're helping out and describing what you intend to test.
  2. 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].
  3. Exercise the software.
  4. 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.
  5. Optional: Consider sending descriptions of your tests to testing@globus.org so that we might use them to build standard tests in the future.
  6. 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 Delegation Service

The Delegation Service is a new component in Globus Toolkit version 3.9.3. This component provides an exposed interface for delegation of credentials to a host. This enables a single delegated credential to be shared across multiple invocations of services on that host (e.g. it could be used for multiple GRAM job submissions or across GRAM and RFT submissions.) It also provides a means for credential renewal.

Reasons for testing Delegation Service

Delegation service is a new component added to the Globus Toolkit in this release. The component was designed with the goal of being able to reduce the overhead of doing GSI Secure Conversation whenever delegated credentials are required. Moreover, a credential can be delegated once and shared across services cohosted with the delegation service, by merely using the endpoint reference to the delegated credential.

This testing call is to seek feedback from users on whether the component meets their needs, in terms of functionality and performance. This also is a forum for tester to put forth Suggestions on additional feature/modifications to be able to achieve the above said goals.

Technology dependencies

The Delegation Service depends on the following GT components:

  • WS Authentication and Authorization Message-Level Security

The Delegation Service depends on the following 3rd party software:

  • Apache Axis

Environment/build parameters and other special conditions to test

  1. Use of various JVMs
  2. Persistence feature of delegation resource
  3. Scalability of delegation service component.

Release notes

Release notes for the 3.9.3 Delegation Service can be found here.