Identity Service: Determine whether/how to expose merge session functionality |
||||||
Issue description- Should Identity Service expose interface for doing a merge session? - Should it just do this in its implementation and not expose it to clients? - Should the implementation be backed by GaiaCookieManagerService or directly by UbertokenFetcher / MergeSession? A couple notes about the above questions: - GaiaCookieManagerService has lots of consumers in the codebase, but most of these are not for doing a merge session - UbertokenFetcher takes in an O2TS, which clients typically pass a PO2TS. This means that we can't get rid of consumers' dependence on PO2TS as long as they're using UbertokenFetcher (OR UbertokenFetcher needs to depend on Identity Service instead).
,
Jun 6 2017
,
Jun 8 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