DevicePolicyManager.IsActivePasswordSufficientForDeviceRequirement Property
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Called by profile owner of a managed profile to determine whether the current device password meets policy requirements set explicitly device-wide.
public virtual bool IsActivePasswordSufficientForDeviceRequirement { [Android.Runtime.Register("isActivePasswordSufficientForDeviceRequirement", "()Z", "GetIsActivePasswordSufficientForDeviceRequirementHandler", ApiSince=31)] get; }[<get: Android.Runtime.Register("isActivePasswordSufficientForDeviceRequirement", "()Z", "GetIsActivePasswordSufficientForDeviceRequirementHandler", ApiSince=31)>]
member this.IsActivePasswordSufficientForDeviceRequirement : boolProperty Value
true if the device password meets explicit requirement set on it,
false otherwise.
- Attributes
Remarks
Called by profile owner of a managed profile to determine whether the current device password meets policy requirements set explicitly device-wide.
This API is similar to #isActivePasswordSufficient(), with two notable differences: <ul> <li>this API always targets the device password. As a result it should always be called on the #getParentProfileInstance(ComponentName) instance.</li> <li>password policy requirement set on the managed profile is not taken into consideration by this API, even if the device currently does not have a separate work challenge set.</li> </ul>
This API is designed to facilite progressive password enrollment flows when the DPC imposes both device and profile password policies. DPC applies profile password policy by calling #setPasswordQuality(ComponentName, int) or #setRequiredPasswordComplexity on the regular DevicePolicyManager instance, while it applies device-wide policy by calling #setRequiredPasswordComplexity on the #getParentProfileInstance(ComponentName) instance. The DPC can utilize this check to guide the user to set a device password first taking into consideration the device-wide policy only, and then prompt the user to either upgrade it to be fully compliant, or enroll a separate work challenge to satisfy the profile password policy only.
The device user must be unlocked (
Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.