Eliminate GetAuthTokenFunction being an OAuth2TokenService::Consumer |
|||||||
Issue descriptionGetAuthTokenFunction should use the Identity Service for all of its requests for access tokens. Note however that this is dependent on us coming up with a plan for DeviceOAuth2TokenService (see blocking bug).
,
Jun 5 2017
,
Jun 5 2017
,
Jun 6 2017
,
Nov 1 2017
,
Nov 7 2017
,
Nov 6
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 6
--Chrome Identity automated triaging-- This available, signin or profiles-related bug has gone at least 30 days since the last automated post without any further update. This bug will be closed out due to inactivity. Please re-open the bug and provide an update if it is still a valid or reproducible bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by blundell@chromium.org
, Jun 5 2017