Get a UCAMS / XCAMS account:
ORNL Staff:
Non-ORNL Staff:
Visit https://xcams.ornl.gov and click on "I need an account." and complete all steps of the registration process
Note
This request is reviewed and may take up to five business days for approval. Remote users who are not ORNL interns and not U.S. citizens, will need an ORNL host to provide them with a Cyber Access PAS from the Visitor’s Center before they can be approved for access to the external login node. ORNL interns who already have a PAS will not need a second one for this.
To get access to the external visitor login nodes, go to https://xcams.ornl.gov/xcams/groups/cades-misc/ and follow the instructions to request an account.
Please follow instructions for setting up the pre-requisites for the data adapter.
Managing and sharing data:
Please use https://globus.org to organize, manage, move, and share data.
Downloading data to workstations:
Users interested in using either the REST API or the python wrapper to the REST API would need to:
In order to get both these elements, users need to:
An API Key is an encrypted string that is a substitute to your username and password for authenticating as yourself into DataFlow. In other words, this is how you will tell DataFlow that you are the person contacting DataFlow. Unlike a username / password, this string is encrypted and does not mean anything to anyone outside the scope of DataFlow. However, should someone else have access to your API key, they will be able to view datasets you created using DataFlow, change some default configurations, and possibly upload data to the destination storage (as yourself) if they also have access to your encrypted password (more below) for your Globus endpoint. Thus, the API Key should be kept safely, perhaps in a text file separate from your scripts. Consider limiting the duration of the API key if you feel that the script / key might be visible to anyone else after a certain point
While the API Key authenticates you to use DataFlow, you would still need to authenticate yourself to use the data adapter (e.g. Globus) that will finally copy data to the destination storage solution. For example, you need to specify appropriate username and password in order to activate Globus endpoints. Since sending passwords as plain-text is unsafe, DataFlow allows you to authenticate via an encrypted password instead.
Given that DataFlow is currently only supported by the Globus data adapter, it is recommended to encrypt passwords relevant to activate the source and destination Globus endpoints. By default, DataFlow uses ORNL XCAMS / UCAMS credentials to activate both the source (DataFlow server) endpoint and the default destination - CADES Open-Research Home. Thus, encrypting just the XCAMS / UCAMS password is sufficient for most users.
However, if you choose to use an alternate destination file-system that uses different (not XCAMS / UCAMS) authentication, you would need to encrypt the password for that endpoint.
In order to encrypt and password, visit the "API access" section of DataFlow.
Note: This encryption capability is not suitable for two-factor authentication steps that require temporary / one-time passwords. For example, OLCF's passcode that is derived from an RSA token.
In order to use the python wrapper to the REST API, users would need to: