Keymaster init for work profile
Changes: (1) When unified work challenge is enabled and screen lock is secure - Store work profile secure key in primary profile - When primary user keystore unlocked, unlock work profile keystore - When primary user change lock to none, remove work secure key (2) When unified work challenge is enabled but screen lock is not secure - When screen lock changes to secure, store work secure key in primary (3) When user changes work challenge from unified to separated - Remove work secure key in primary (4) When user changes work challenge from separate to unified - Do (1) and (2) Bug: 27460698 Change-Id: Id7464c178e6ea7b561643477e7cd84f963048c87
This commit is contained in:
@@ -68,7 +68,6 @@ abstract class SaveChosenLockWorkerBase extends Fragment {
|
||||
mHasChallenge = hasChallenge;
|
||||
mChallenge = challenge;
|
||||
// This will be a no-op for non managed profiles.
|
||||
mUtils.setSeparateProfileChallengeEnabled(mUserId, true);
|
||||
mWasSecureBefore = mUtils.isSecure(mUserId);
|
||||
|
||||
Context context = getContext();
|
||||
|
Reference in New Issue
Block a user