diff options
| author | joaodasilva@chromium.org <joaodasilva@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-15 17:29:29 +0000 |
|---|---|---|
| committer | joaodasilva@chromium.org <joaodasilva@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-15 17:29:29 +0000 |
| commit | 28d9fc63e36aa686c725c87f54ffadde7b4498ed (patch) | |
| tree | dc440610d31f7e00ba65426395549076def2d690 /net/socket/socks_client_socket_pool.cc | |
| parent | 714e3843f9f26e98c29d053f03d1360929f418bc (diff) | |
| download | chromium_src-28d9fc63e36aa686c725c87f54ffadde7b4498ed.zip chromium_src-28d9fc63e36aa686c725c87f54ffadde7b4498ed.tar.gz chromium_src-28d9fc63e36aa686c725c87f54ffadde7b4498ed.tar.bz2 | |
UserPolicyCache only becomes ready after policy has been fetched.
This behavior is only forced on enterprise devices, and for logged in users whose username matches the enrollment domain.
This requires waiting for a couple of things:
- oauth token fetching
- dm server register token fetching
- user policy fetching
The cache resumes initialization too if any of these steps fails. Fetching of OAuth tokens usually happens after Profile creation, but in this case it will be done earlier so that the policy fetching can proceed before the Profile is fully created.
This fixes the races between policy and sync, startup pages, etc.
BUG=chromium-os:17698
TEST=Logins of enterprise users on enrolled ChromeOS devices waits for a policy fetch before proceeding.
Review URL: http://codereview.chromium.org/8499021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@110108 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/socket/socks_client_socket_pool.cc')
0 files changed, 0 insertions, 0 deletions