Maybe just throw it away since we don't need it? That'd be safest. Or mint it in case it's valuable in the future, but don't inject it into user sessions.

Let's forego the robot account altogether and just don't request one during enrollment.  If we decide we need it later on, we can always add it back.  (Backward compatibility won't be a huge issue since the initial amount of Chromad devices will be small anyways.)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c7d62e1924975b2920f0b5e7690d211c75007408

commit c7d62e1924975b2920f0b5e7690d211c75007408
Author: rsorokin <rsorokin@chromium.org>
Date: Thu Jan 12 14:08:38 2017

Don't fetch robot account for the Active Directory managed devices.

BUG= 676382 
TEST=none

Review-Url: https://codereview.chromium.org/2625123003
Cr-Commit-Position: refs/heads/master@{#443221}

[modify] https://crrev.com/c7d62e1924975b2920f0b5e7690d211c75007408/chrome/browser/chromeos/policy/enrollment_handler_chromeos.cc

bulk Verify of Chromad V1 bugs