The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/5cc8b4624a642de01ba357c36224cb43d75cd681

commit 5cc8b4624a642de01ba357c36224cb43d75cd681
Author: Alex Mineer <amineer@google.com>
Date: Fri Feb 02 19:34:14 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/1f55d79494aabc4388066b9f13fc64f122ab2556

commit 1f55d79494aabc4388066b9f13fc64f122ab2556
Author: Alex Mineer <amineer@google.com>
Date: Fri Feb 02 22:27:15 2018

Verification request has been submitted, should take 3-7 days to process.  Will keep this open until finished.

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I think we're good here.

It appears some people are still seeing this.  We've discovered that if you authorized Chromium Dash in the past, it likely requested permission for a scope considered dangerous (Project Hosting) which we thought was required to query Monorail but, as it turns out, is not.  We removed that scope from the request months ago, but apparently the scope persists if you've authorized Chromium Dash in the past.

To avoid this, visit https://myaccount.google.com/permissions?pli=1 for the account you want to log in with - you should see an entry for Chromium Dash that looks like the attachment (note the Google Code entry there).  Press "Remove Access" and then attempt to log in again - you should no longer see the warning.

Deleted: Screen Shot 2018-03-01 at 8.42.52 AM.png 119 KB

	Screen Shot 2018-03-01 at 8.42.52 AM.png 119 KB View Download

 Issue 817221  has been merged into this issue.