Description

Currently, when trying to list the contents of a collection that is in a mapped collection that requires consent DataFed is unable to provide access. This is because the feature allowing the full consent flow and obtaining a token with consent rights is not supported. This feature would seek to change this behavior so that as a first step a user when running a data put or data get from the web ui would get redirected to globus where the user would grant consent and get passed back to DataFed, The datafed client would store the creds and make a call to list the contents of the collection, the contents would come back from Globus and be viewable in the DataFed web, file browser.

Current steps to show case the problem are shown below.

Acceptance

• Selecting a mapped collection in the browser will check to see if a user has access using their default token
• Access to default token works, flow continues as normal
• Consent required, the consents needed are identified
• Request sent to Globus API specificying the required consents, i.e. what IP or globus identities the user must login with
• Upon user finishing the flow with Globus, DataFed fetches the collection contents whereby the user can see the files
• Selection of a file should then fail with an alert indicating that transfers are not yet supported. (Intermediate step) and the user should be returned to the dashboard back to the file browser.