diff options
| author | mnissler@chromium.org <mnissler@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-19 09:36:41 +0000 |
|---|---|---|
| committer | mnissler@chromium.org <mnissler@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-11-19 09:36:41 +0000 |
| commit | c6e06465864cace956a85669afe55007b57ea5a0 (patch) | |
| tree | 31b4f9b406de0b59787979b94d4a88be878aa61c /testing/gmock_mutant.h | |
| parent | ea55d4577c4cbe7d1b6cafa97514e1bcfe7b5b4b (diff) | |
| download | chromium_src-c6e06465864cace956a85669afe55007b57ea5a0.zip chromium_src-c6e06465864cace956a85669afe55007b57ea5a0.tar.gz chromium_src-c6e06465864cace956a85669afe55007b57ea5a0.tar.bz2 | |
Move DeviceManagementPolicyProvider into the profile.
Previously, we used only one provider, which would break in situations where there are two profiles (which ChromeOS already does), because it would apply the policy to both profiles and not only the logged in one. For this to work properly, we also need to pass the relevant TokenService instance the DeviceTokenFetcher, so the fetcher can decide whether the token is relevant to it by checking whether the TokenService that sent it is the one associated with the right profile.
BUG=63608
TEST=existing unit tests succeed
Review URL: http://codereview.chromium.org/5174006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@66755 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'testing/gmock_mutant.h')
0 files changed, 0 insertions, 0 deletions