New issue
Advanced search Search tips

Issue 690030 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Authenticate requests to /testfile/upload

Project Member Reported by serg...@chromium.org, Feb 8 2017

Issue description

Currently we just use whitelist, but should instead distribute a service account to all bots and authenticate with it before upload test results to test result server.

This approach is more flexible and will allow us to deploy test service accounts for testing uploading locally.
 
Issue 689120 has been merged into this issue.
Project Member

Comment 2 by sheriffbot@chromium.org, Feb 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
We should probably use task account for this after we migrate to LUCI.
Cc: seanmccubb@google.com
Status: Available (was: Untriaged)
Cc: -seanmccubb@google.com seanmccullough@chromium.org
I'd like to do away with the /testfile/upload step altogether but if we can't, we should definitely auth these requests.

Sign in to add a comment