diff options
| author | Esteban Talavera <etalavera@google.com> | 2017-01-24 16:47:16 +0000 |
|---|---|---|
| committer | Esteban Talavera <etalavera@google.com> | 2017-01-25 12:07:37 +0000 |
| commit | b88f42b6b1414ae8107be13c0d2f3957549ecaaf (patch) | |
| tree | bc203e46580f8fb4cfe951c7b0c9854d96cd0fcb /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | c3f3595153a5a5b2c7bbeab628e96cf711670fd4 (diff) | |
Wipe device or profile if max failed attempt reached
If the device or profile owner have set a max password failed
attempts policy, the device or profile should be wiped even if
DISALLOW_FACTORY_RESET / DISALLOW_REMOVE_USER /
DISALLOW_REMOVE_MANAGED_PROFILE was set by that admin. However
it should still fail if another device admin set the policy - this
is in line with what wipeData() does at the moment.
Bug: 34450538
Test: runtest -c com.android.server.devicepolicy.DevicePolicyManagerTest frameworks-services
Test: cts-tradefed run cts --module DevicePolicyManager --test com.android.cts.devicepolicy.DeviceOwnerPlusManagedProfileTest#testWipeData
Test: cts-tradefed run cts --module DevicePolicyManager --test com.android.cts.devicepolicy.ManagedProfileTest#testWipeData
Test: cts-tradefed run cts --module DevicePolicyManager --test com.android.cts.devicepolicy.DeviceOwnerTest#testDisallowFactoryReset
Change-Id: Ifac240692ce74432f7b57f3dfbbbac2a7282297b
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions