New issue
Advanced search Search tips

Issue 868718 link

Starred by 1 user
Status: Duplicate
Merged: issue 780792
Owner:
poromov@chromium.org
Closed: Jul 31
Cc:
atwilson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome policies fail to be applied after renaming a user

Reported by nick.sem...@gmail.com, Jul 29 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36

Steps to reproduce the problem:
1. Sign in to chrome & sync to an account w/ enterprise policies
2. Rename the account (in the admin console)
3. Note that policy sync no longer works in chrome://policy

What is the expected behavior?

What went wrong?
At chrome://policy the old username is shown, with the error: "Validation error: Wrong policy subject"

Did this work before? N/A 

Chrome version: 68.0.3440.75  Channel: stable
OS Version: 10.0
Flash Version:

Comment 1 by pastarmovj@chromium.org, Jul 30

Owner: atwilson@chromium.org
Status: Assigned (was: Unconfirmed)
I think this topic has been discussed in the past as well. Drew do you know if the server side folks should look into that?

Comment 2 by atwilson@chromium.org, Jul 31

Cc: atwilson@chromium.org
Owner: poromov@chromium.org
So, when we rename the account, are we just changing the username, or the domain, or both?

Sergey, I'm surprised that this doesn't work given your fix here: https://chromium-review.googlesource.com/c/chromium/src/+/980873 - maybe the existing policy doesn't have a gaia ID in it somehow?

Comment 3 by poromov@chromium.org, Jul 31

Status: Fixed (was: Assigned)
Sending GAIA ID on server side is enabled only for a couple of TT domains - we want to extensively test it as it was dangerous change that could break lots of devices.
So, unfortunately the bug is still reproducible for most of customers. As soon as QA will give green light, server side fix (enable for all) will resolve it.

Comment 4 by atwilson@chromium.org, Jul 31

Mergedinto: 780792
Status: Duplicate (was: Fixed)
OK, so I guess we're waiting for M68 to go stable before we start dialing this up?

Comment 5 by poromov@chromium.org, Jul 31 

The exact bug from above should be fixed in M67 already, but the fix will work only when server will start sending gaia id for everyone.
►

Sign in to add a comment