New issue
Advanced search Search tips

Issue 648926 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Change Chrome OS login to extract dasher status from the id_token rather than from a Gaia call

Project Member Reported by atwilson@chromium.org, Sep 21 2016

Issue description

A recent Kansas outage resulted in signins failing because the userinfo call we use to verify user whitelists was returning an error.

Guidance from Gaia is to use the id_token returned when we mint our refresh token, and parse/extract the hd parameter from that instead, saving an extra backend call.

Looks like we can extract that information and store it in UserContext and pass this through into the LoginPerformer.

 
Cc: atwilson@chromium.org
Owner: antrim@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment