New issue
Advanced search Search tips

Issue 681533 link

Starred by 2 users

Issue metadata

Status: Closed
Owner: ----
Closed: Aug 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chromad: Investigate whether we need device_id in install attributes

Project Member Reported by tnagel@chromium.org, Jan 16 2017

Issue description

.
 

Comment 1 by tnagel@chromium.org, Jan 16 2017

The device id (aka client id) seems to come down from DM server during enrollment.  From what I can see, it's only used in enterprise platform keys private API EPKPChallengeKeyBase::GetDeviceId().

Comment 2 by tnagel@chromium.org, Jan 17 2017

Labels: -Pri-1 -M-57 M-58 Pri-3
After discussion with David: Let's keep it for now, maybe re-discuss for M-58.  (I'm still not 100% sure what it's needed for, but attestation seems to be one use case.)

Comment 3 by tnagel@chromium.org, Jul 26 2017

Owner: ----
Status: Available (was: Assigned)
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 26

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: ljusten@chromium.org
Status: Closed (was: Untriaged)
I thinkg it's obsolete

Sign in to add a comment