-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix dcp-diag tool ingest authentication #372
Comments
Possible solutions: Option 1: Do not supply token in the GET requests.
Pros: much quicker than option 2 Option 2: Use DCP Fusillade Auth for user authentication
Pros: This is the proper solution in my opinion. X Option 3: Provide GCP Service account to wranglers
Cons: very insecure |
In my opinion, definitely not option 3. We have many other priority task so I suggest option 1 and kick the can down the road to when it actually becomes necessary. |
PR for option 1 - https://github.com/HumanCellAtlas/dcp-diag/pull/17/files |
Released a new version of DCP Diag tool: dcp-diag==1.0.1 https://github.com/HumanCellAtlas/dcp-diag/blob/master/Changes.md#changes-for-v101-2019-04-02 Verified that error is no longer happening:
@zperova @hewgreen this is now fixed. Please upgrade your version of
Thanks! |
@aaclan-ebi thanks! I will upgrade now and try it for my bundle in integration. |
@aaclan-ebi I can run what you have tested with no problem, but when I try to test my submission in integration I get the following error:
|
@zperova, please use
Filed an issue in the dcp-diag repo for now. |
@aaclan-ebi good point! it works. |
https://humancellatlas.slack.com/archives/C6YTC4NJW/p1553733826258300
Steps To Reproduce:
analyze-submission -d prod 5bfe4d3a9460a300074eebc8
Actual Behavior:
the
analyze-submission
feature in the dcp-diag tool is returning the error:Expected Behavior:
No authentication error
The text was updated successfully, but these errors were encountered: