Support POST'ing of Passports to DRS endpoints

[briandoconnor]

DEADLINE: please comment on the PR #363 before the next Cloud call on Sept 13th. We will merge this PR then if there are no blocker comments.

In the TOPMed (BioData Catalyst) driver project (and applicable to GDC and NCI Drivers) we have been exploring different ways of interacting between Passport systems (NIH RAS in this case) and a DRS server. There are multiple proposals for how a Passport with Embedded Visas should be handed to a DRS server and BDCat has documented 3 different approaches we're considering here. We've largely settled on an approach where RAS Passports will be POST'd directly to a DRS server, see here.

In the RAS passport to DRS server flow (option 2, scenario 1) we would need a way to POST a RAS Passport to a DRS server and right now the /objects/{object_id}/access/{access_id} only supports GET.

This issue is accompanied by a feature branch feature/issue-348-post-passport-v2 where I'm trying to update the schema to accommodate posts.

You can follow builds on Travis

Built docs can be found at preview/feature/issue-348-post-passport-v2/docs

Swagger schema can be downloaded from the top of the docs above and visualized at https://editor.swagger.io

The PR: #363

[ianfore]

Would this just be for Passport? Or are we offering POST for the other auth mechanisms that currently exist e.g. the payloads that are currently passed via Bearer tokens?

Can we assume that the passing of auth'n for GETs continues to exist?

[briandoconnor]

PR was merged so closing