The NSF GAGE and SAGE Facilities, operated by EarthScope Consortium, formerly UNAVCO and IRIS respectively, are transitioning to a data access model that requires data users to register and log in (known as Identity Management or simply IdM). We have developed an IdM system that allows users to register for both the NSF GAGE and SAGE facilities. Data systems that begin using this IdM will be announced prior to their release.
The NSF GAGE Facility's first release of IdM is for its HTTPS data file server: gage-data.earthscope.org. See the file server transition announcements.
To test logging in to gage-data.earthscope.org you will need to register a user account with us. Then you can browse the HTTPS server's web pages and access the file server programmatically from the command line, see our examples. Please send your issues, comments, and suggestions to: software@earthscope.org.
You can use an existing identity provider (CILogon or Google) or sign up to register an account directly with us. This will create a user profile for you.
On our Data File Server log on page you can either:
A) Use Your Existing Identity
If your organization uses Google or CILogon as an identity provider:
B) Create an Identity with EarthScope
Access your user profile page to manage your account information, access API Keys, and allow you to delete your account.
We display an API key in your user profile. This API key is a short-lived access token that you can copy and paste into http get request headers to try out accessing our file server. However, we recommend our Command Line Interface (CLI) for long running script access.
For systems that use this new IdM, there will be a Login link or button on the top of related web pages, or the login/signup page will be automatically displayed, as it is on gage-data.earthscope.org.
For command line access, see our Command Line Interface (CLI) (or SDK for developers) to simplify access token acquisition and managemet for unattended data access scripts. See our HTTPS File Server Access Examples for how to get files.
We are working on implementing Single Sign On (SSO) across web systems, so that your user session state (logged in or logged out) is shared across our organization.
Last modified: 2024-04-12 16:14:35 America/Denver