Globus Connect Server Endpoints Now Support Migration to gaccess.io

In July 2025, we announced that new Globus Connect Server (GCS) endpoints would receive default domains under gaccess.io. Starting with GCS version 5.4.100, administrators can now migrate most endpoints under data.globus.org or dn.glob.us domains to gaccess.io. See our Domain Migration guide for more details and instructions on how to migrate.

What’s changing

Only the suffix of your Globus-issued domain changes. For example, a collection at m-4283f.9009.09ad6.data.globus.org becomes m-4283f.9009.09ad6.gaccess.io. This applies to your endpoint domain (including the management API) and to all mapped and guest collections using Globus-issued domains.

How migration works

Migration has two phases, allowing you to test the new domain and update external domain references before cutting over.

Phase 1: Allocate the New Domain (Automatic). Globus Connect Server performs this automatically when the updated Globus Connect Server packages are installed. Your endpoint is issued a gaccess.io name and begins answering on both its old and new names.

Phase 2: Retire the Old Domain (Admin-Initiated). Once any applications have been updated to use the new domain, you retire the old domain name and only the gaccess.io name remains.

What to update during the transition

Between phases 1 and 2, both the old and new domains work. This is the window to update anything that references your endpoint or collection hostnames to use the new gaccess.io domain.

Administrators should update anything they manage directly, such as firewall or proxy allowlists and scripts that call the GCS management API.

Notify your users. Before completing migration (phase 2), let your user community know about the domain name change and instruct them to update any references to collections that live in applications and resources that they manage. Give them the new gaccess.io domains for the collections they use and a deadline for making updates. Things they may need to update include data portals, search indices, HTTPS download links, published dataset or DOI landing pages, and their own scripts or workflows that use collection hostnames. Allow enough time for your users to make changes before you retire the old domain.

Globus Transfer tasks use collection IDs, and therefore, are not affected by domain migration.

Details and instructions are found in the Domain Migration guide. Please contact support@globus.org with any questions.