Issue 173267 in chromium: Invalid Device management token error on ChromeOS device pointing to staging

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
CC: scunning...@chromium.org, sfir...@chromium.org, t...@chromium.org
Labels: Type-Bug Pri-2 Area-Internals OS-Chrome Feature-Enterprise

New issue 173267 by krishna...@chromium.org: Invalid Device management
token error on ChromeOS device pointing to staging
http://code.google.com/p/chromium/issues/detail?id=173267

Version: R25.0.1364.57;3428.110.0;Link
OS: ChromeOS

Summary:
Invalid Device management token error on the chrome://policy page.
Device is pointing to staging.(cros-dev)
At around Timestamp -0130/111003--> 401 response from the DM server -in
chrome logs.

What steps will reproduce the problem?
1.Enroll a device to staging to a domain which has Public Accounts enabled.
2.After a couple of hours/good night's sleep come back and continue to use
the device while observing the Status on the chrome://policy page during
each log in and log out.

What is the expected output? What do you see instead?
The Policies should be fetched

Actual Output: Policies are not fetched and getting a 401 from the DM
server.

Please use labels and text to provide additional information.

Attached Screenshot and logs

Attachments:
Screenshot 2013-01-30 at 11.00.46 AM.png 257 KB
log-013013-113800.tar.bz2 3.3 MB

[chro...@googlecode.com]

Comment #1 on issue 173267 by t...@google.com: Invalid Device management

token error on ChromeOS device pointing to staging
http://code.google.com/p/chromium/issues/detail?id=173267

cros-dev last received a request from this device at around 10:29, and the
fetch was successful.

[chro...@googlecode.com]

Updates:
Cc: chromeos...@google.com mnis...@chromium.org

Comment #2 on issue 173267 by t...@chromium.org: Invalid Device management

token error on ChromeOS device pointing to staging
http://code.google.com/p/chromium/issues/detail?id=173267

A lot of requests were hitting prod from this machine around 11. Somehow
the DM path was reset to PROD. Did you do anything that may have caused
this?

[chro...@googlecode.com]

Comment #3 on issue 173267 by krishna...@chromium.org: Invalid Device

management token error on ChromeOS device pointing to staging
http://code.google.com/p/chromium/issues/detail?id=173267

Looking at the update_engine logs(update_engine.20130130-101554), there
was an Auto Update from version -3428.108.0 to 3428.110.0. @ around 10:29AM.

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #4 on issue 173267 by mnis...@chromium.org: Invalid Device

management token error on ChromeOS device pointing to staging
http://code.google.com/p/chromium/issues/detail?id=173267

Well, the auto-update obviously resets the DMServer URL to prod, so this
behavior is expected. Closing WontFix.