diff options
| author | Clara Bayarri <clarabayarri@google.com> | 2016-02-23 14:49:41 -0800 |
|---|---|---|
| committer | Clara Bayarri <clarabayarri@google.com> | 2016-02-29 10:06:54 -0800 |
| commit | 0a587d2840ca105746a9e14d018dc8ec2b3442be (patch) | |
| tree | e300b1811b347934f597e54484d2718e664625ff /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 342006e91990f59b2e71c76a7d8589f7de571246 (diff) | |
Unlock Keystore/Keymaster separately for Work Challenge
The Keystore should be unlocked by the work challenge when
the work profile has its own lock, and should not be unlocked
by the device lock in this case.
Tested use cases:
When unified, both users have the password key set to the parent's
Setting a work challenge changes the work profile's password key to its
own
Unifying causes the work challenge key to be set to null first and then
when the device password is reset right after that it is reset to the
same as the parent
Unlocking when locks are unified unlocks both using the same password
key
Unlocking the device when not unified only unlocks the parent
Unlocking the work challenge only unlocks the work profile
Bug:26817206
Change-Id: I99dca279687f4f77636992e355dbdb607bbf7b6d
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions