Loading core/java/android/os/UserManager.java +13 −4 Original line number Diff line number Diff line Loading @@ -1539,10 +1539,19 @@ public class UserManager { * Specifies that the managed profile is not allowed to have unified lock screen challenge with * the primary user. * * <p><strong>Note:</strong> Setting this restriction alone doesn't automatically set a * separate challenge. Profile owner can ask the user to set a new password using * {@link DevicePolicyManager#ACTION_SET_NEW_PASSWORD} and verify it using * {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)}. * <p>To ensure that there is a separate work profile password, IT admins * have to: * <ol> * <li>Enforce {@link UserManager#DISALLOW_UNIFIED_PASSWORD}</li> * <li>Verify that {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)} * returns true. This indicates that there is now a separate work * profile password configured and the set up is completed.</li> * <li>In case {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)} * returns false, invoke {@link DevicePolicyManager#ACTION_SET_NEW_PASSWORD} * intent and then verify again * {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)}.</li> * </ol> * </p> * * <p>Can be set by profile owners. It only has effect on managed profiles when set by managed * profile owner. Has no effect on non-managed profiles or users. Loading Loading
core/java/android/os/UserManager.java +13 −4 Original line number Diff line number Diff line Loading @@ -1539,10 +1539,19 @@ public class UserManager { * Specifies that the managed profile is not allowed to have unified lock screen challenge with * the primary user. * * <p><strong>Note:</strong> Setting this restriction alone doesn't automatically set a * separate challenge. Profile owner can ask the user to set a new password using * {@link DevicePolicyManager#ACTION_SET_NEW_PASSWORD} and verify it using * {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)}. * <p>To ensure that there is a separate work profile password, IT admins * have to: * <ol> * <li>Enforce {@link UserManager#DISALLOW_UNIFIED_PASSWORD}</li> * <li>Verify that {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)} * returns true. This indicates that there is now a separate work * profile password configured and the set up is completed.</li> * <li>In case {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)} * returns false, invoke {@link DevicePolicyManager#ACTION_SET_NEW_PASSWORD} * intent and then verify again * {@link DevicePolicyManager#isUsingUnifiedPassword(ComponentName)}.</li> * </ol> * </p> * * <p>Can be set by profile owners. It only has effect on managed profiles when set by managed * profile owner. Has no effect on non-managed profiles or users. Loading