Summary
Implement the OAuth 2.0 authorization code flow against Azul's /user/authorize endpoint for HCA DCP dev, mirroring what was done for AnVIL in #4793 / #4796.
This was originally part of the scope of #4793 ("This should be implemented for HCA and AnVIL"); #4796 covered AnVIL only. This ticket tracks the HCA DCP dev half.
Context
Scope
Out of scope
- HCA DCP prod (and other non-dev HCA envs) — to be tracked separately if/when the flow is rolled out beyond dev
Test plan
Mirror #4796:
References
Summary
Implement the OAuth 2.0 authorization code flow against Azul's
/user/authorizeendpoint for HCA DCP dev, mirroring what was done for AnVIL in #4793 / #4796.This was originally part of the scope of #4793 ("This should be implemented for HCA and AnVIL"); #4796 covered AnVIL only. This ticket tracks the HCA DCP dev half.
Context
Scope
site-config/hca-dcp/dev/authentication/constants.ts:flowtoOAUTH_FLOW.AUTHORIZATION_CODEauthorizeURL pointing at the HCA DCP dev Azul/user/authorizeendpointCLIENT_IDto whatever is required for the new flow (TBC with @hannes-ucsc)cc-ma-dev,ma-prod,cc-dev, etc.) remain onOAUTH_FLOW.IMPLICITfor now, per the "only Azuldev/anvildevshould adopt this" guidance from Implement authorization code flow with Azul and Data Browser #7954 #4793Out of scope
Test plan
Mirror #4796:
localhost:3000against HCA DCP dev: POST to/user/authorizereturns{access_token, id_token, scope, expires_in, token_type}; profile loadsReferences