- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide (coming soon)
- Migrating from GT2
- Migrating from GT3
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces (coming soon)
- Resource Properties
- Performance Studies (coming soon)
- Non-WS (General) Security
- WS Java Security
- Authz Framework
- Delegation Service
Table of Contents
Nothing should have to be done when migrating from GT2.
This version is not compatible with the GT2 version of CAS because of protocol changes. To migrate to this version, this component needs to be installed completely independent of any current GT2.x CAS installs.
GT2 and GT3 services were set up to run with root owned host credentials. In GT4 most,
but not all, services will run as the globus user. To allow the
globus user to start services using host credentials the globus user needs to be able to access them. This requirement can be satisfied by making a copy of the root owned host credentials, i.e. the host certificate and private key, owned by the globus user. In GT4 this copy is assumed to be
No special procedures are required for MyProxy installations migrating from GT2 to GT4. MyProxy is backward compatible.