Sync requests failing for new Supervised Users
Reported by
nicods.2...@gmail.com,
Oct 5 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Create a new supervised user in chrome 2. Apply restrictions from https://chrome.google.com/manage 3. Go to your supervised profile and try to access to an unauthorized site What is the expected behavior? An authorization request page should be displayed What went wrong? You can access to the page normally. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 27.0 r0 - That happen just in new supervised profiles. Existing profiles are working and apply the new rules normally. - We've confirmed that in Windows,Mac and ChromeOS (Chrome 60.0.3112.114). - Happen with all the restrictions type. - That was reported from the support forum: https://productforums.google.com/d/msg/chrome-es/qOZPXKFlzXc/qy7mRbpFAAAJ - Sync internals seem is not working Example profile id: QPXL78O3Gdg
,
Oct 6 2017
Nico, you confirmed that this happens in Chrome *60* as well? Nicolas, Jeremy, are you aware of any Sync changes recently that might affect newly created supervised users?
,
Oct 6 2017
I got the same result when testing on my Linux machine. (Also adding the current primary for Playpen smoke testing :-D)
,
Oct 6 2017
Hi bauerb! Thanks for you answer! ChromeOS actually is running Chrome 60.0.3112.114. Sadly, i've no access to Chrome 60 in any desktop (Mac/Windows/Linux). Sorry! Anyway, i can assert that new profiles (No supervised) are working well with Synchronisations, just supervised users are unable to get a new Sync Client ID. Sync server error maybe?
,
Oct 6 2017
Yes, I looked at the network traffic (using chrome://net-internals), and the Sync server is returning a 500 error. I'll file an internal bug against the server.
,
Oct 6 2017
Filed b/67497857.
,
Oct 6 2017
,
Oct 8 2017
Same problem trying to manage supervised user on chromebook
,
Oct 9 2017
Hi everyone, we're aware of this issue and working on a fix. If you are affected by this, please star the issue instead of commenting, as that is easier to track and creates less noise. Thanks!
,
Oct 9 2017
,
Oct 9 2017
,
Oct 19 2017
Sorry, I forgot to update this bug: this should be fixed now. Thanks!
,
Oct 19 2017
Yeah, you will have to delete and re-import the profile, because its auth token is invalid :-/ Once you do that, the newly generated profile should get the right restrictions right away though.
,
Oct 19 2017
Sorry to be dense but can anyone tell me how to do this...
,
Oct 19 2017
Oh! That's a little tricky, i'm thinking about the forum's users that have reported that. I understand, the auth token can't be regenerated in other way. I'll inform that to they. Thanks again for your hard work!
,
Oct 19 2017
@fionania check "Remove someone from Chrome" in https://support.google.com/chrome/answer/2390059?co=GENIE.Platform%3DDesktop&hl=en Anyway, you can get help about how do that in the Chrome Support Forum: https://productforums.google.com/forum/#!forum/chrome :) |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by meh...@chromium.org
, Oct 6 2017