ESGF_GO_Admin

Wiki Reorganisation
This page has been classified for reorganisation. It has been given the category MOVE.
The content of this page will be revised and moved to one or more other pages in the new wiki structure.

Configuring Globus Online on your ESGF Portal (for Administrators)

If you are an ESGF Node Administrator and you would like to configure your node for use with Globus Online, the below documentation is for you.

_ NOTE: your data must already be accessible by way of one (or more) GridFTP servers in order to be transferrable using the ESGF Portal Globus Online integration. For more information about preparing your data, please read the documentation on _ Data Publishing .

Most prerequisites to enabling the Globus Online transfer method within the ESGF portal are automatically handled by the ESGF installer (version 1.5 and later). The Administrator needs only to perform a couple of simple configuration steps.

1. You must create a Globus Online account for your portal node:

   In order for oAuth to work correctly such that the user does not have to link their ESG credential with their Globus Online account, the portal must have its own account. This should be a separate account that is used only for the portal. https://www.globus.org/SignUp

2. You should run:

   esg-node --install-globus-online

   This will do three things:

   • It will create the /esg/config/globusonline.properties file to configure the portal to use the Globus Online account and password you created above. It will be readable by the tomcat user (but not by everyone) and contain the following:

     GOesgfPortalID=username

     GOesgfPortalPassword=password

   • It will install /usr/local/bin/mkproxy which is necessary to properly delegate the user's credential to Globus Online to activate the source endpoint.

   • It will put "enableGlobusOnline true" in /esg/config/searchconfig.properties file to enable the Globus Online functionality in the portal.

3. As a final step, you must send your portal's hostname, and the GOesfdPortalID username (but not the password) to [email protected] to request that they add your portal to their oAuth whitelist. A sample message follows:

   As node administrator of the ESGF node HOSTNAME, I'd like to request that our node be added to the oAuth whitelist. The URL that will be redirecting to Globus is http://HOSTNAME/esgf-web-fe/goauthview2, and the Portal's Globus username is USERNAME.