Identity Service: Determine approach to OAuth2MintTokenFlow as used in identity extension API impl |
||||
Issue description
- This class mints a custom-scoped access token based on a login-scoped
access token
- It's only used by the Identity extension API impl
- It's not clear what difference is being what this class is doing and what OAuth2TokenService is doing
- Could we port Identity extension API impl to use O2TS instead for its use case and eliminate this class?
- If not, should we expose functionality of this class via Identity Service?
One note on the above: this class sends a particular callback to GetAuthTokenFunction that the latter class uses to kick off the user consent flow (OAuth2MintTokenFlow::Delegate::OnIssueAdviceSuccess()). It's not clear whether *that* flow is supported by OAuth2TokenService (or any other signin class) at the moment.
,
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 6 2017