As discussed on Slack, in order to address the impractically short lifetime of a curl download command line (DataBiosphere/azul#7945), Azul needs to be able to refresh the user's access token. The only way to achieve this is for Azul to obtain a refresh token and the easiest way to achieve that is to implement the authorization code flow, which involves both the frontend and the backend. We recently added the necessary backend endpoint (DataBiosphere/azul#7954). It is documented on our Swagger UI.
I've also created proof-of-concept patches against this repo and findable-ui. The changes are minimal.
This should be implemented for HCA and AnVIL. For AnVIL, it is on the critical path to the "mirror MA" effort (https://github.com/DataBiosphere/azul-private/issues/359).
As discussed on Slack, in order to address the impractically short lifetime of a
curldownload command line (DataBiosphere/azul#7945), Azul needs to be able to refresh the user's access token. The only way to achieve this is for Azul to obtain a refresh token and the easiest way to achieve that is to implement the authorization code flow, which involves both the frontend and the backend. We recently added the necessary backend endpoint (DataBiosphere/azul#7954). It is documented on our Swagger UI.I've also created proof-of-concept patches against this repo and findable-ui. The changes are minimal.
This should be implemented for HCA and AnVIL. For AnVIL, it is on the critical path to the "mirror MA" effort (https://github.com/DataBiosphere/azul-private/issues/359).