New issue
Advanced search Search tips

Issue 729549 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 809452

Blocking:
issue 683124
issue 809461
issue 729550



Sign in to add a comment

Identity Service: Should device identity become part of the Identity Service?

Project Member Reported by blundell@chromium.org, Jun 5 2017

Issue description

- This class is a subclass of OAuth2TokenService.
- It is ChromeOS-specific and satisfies requests for access tokens by getting them off the device in some fashion.
- If it's *not* going to be in the Identity Service, we'll need to figure out how to decouple it from OAuth2TokenService, since OAuth2TokenService *will* become part of the internal implementation of the Identity Service in the long term.
- Not clear how to handle this offhand.

 
Labels: IdentityService
Blocking: 683124
Blocking: 729550
Components: Services>SignIn
Components: Internals>Services>Identity
Blockedon: 809452
Summary: Identity Service: Should device identity become part of the Identity Service? (was: Identity Service: Should DeviceOAuth2TokenService become part of the Identity Service?)
All of the above apply to DeviceIdentityProvider as well, which is an IdentityProvider subclass that is backed by DeviceOAuth2TokenService.
Blocking: 809461

Sign in to add a comment