Store DM token received during enrollment in local state. |
||||||
Issue descriptionFor cloud mgmt, the DM token is stored as part of the policy blob, however for AD mgmt, the policy blob is under control of the AD server and thus we have to store the DM token in local state (similar to robot account refresh token). We should follow the example of the refresh token and encrypt it, though.
,
Dec 19 2016
,
Jan 9 2017
,
Jan 10 2017
,
Jan 16 2017
,
Feb 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/413a99ab0e025df2ca556a90168ee1174fcc76a6 commit 413a99ab0e025df2ca556a90168ee1174fcc76a6 Author: rsorokin <rsorokin@chromium.org> Date: Fri Feb 10 11:34:17 2017 Rewrite message regarding failure to store DM token BUG= 666281 Review-Url: https://codereview.chromium.org/2672633005 Cr-Commit-Position: refs/heads/master@{#449590} [modify] https://crrev.com/413a99ab0e025df2ca556a90168ee1174fcc76a6/chrome/app/chromeos_strings.grdp [modify] https://crrev.com/413a99ab0e025df2ca556a90168ee1174fcc76a6/chrome/browser/ui/webui/chromeos/login/enrollment_screen_handler.cc
,
Jul 6 2017
bulk Verify of Chromad V1 bugs |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tnagel@chromium.org
, Nov 21 2016