ga4gh / fasp-clients Goto Github PK

See usage of options in GA4GH StarterKit implementation and tutorial.
See ii) here

@ianfore's progress on this currently blocked by getting the iRODs implementation running. Have suggestion from Mike to 'docker pull' the images.

Note differences in how Passport is passed in the two known DRS implementations using Passport

• SRA DRS - see fasp.loc.SRADRSClient
  Syntax is - {"ga4gh_passport": access_token}
• GA4GH StarterKit
  See Step 12 here

It is not clear which DRS spec either of these implementations is targeting. Suggest that needs to be addressed before definitive support is provided in the client.

Method really only check to see if the client has currently been authorized.
Then calls base class get_access_url()
The check can be generalized into the base.

Options include

• Local file
• GA4GH registry
  See the following for DRS entries in registry http://registry.ga4gh.org/v1/services?type=org.ga4gh:drs:*
• Possibly identifiers.org or Bioregistry.io (needs investigation)

Note that client sub-class required depends on the server.
There may be sufficient information in registry to drive this.

Authorization for get_object is currently specific to SBDRSClient.

Could generalize to base class.

Approaches

1. Try no auth first then try with auth2.
   Performance?
2. Record as a property of the DRS server
   get_object then performs auth if necessary
3. Once discovered as in 1, cache this information and take the approach in 2