Accept complex characters policy regardless of password mode
* We were rejecting complex characters policy if the mode was none or simple, but this case is already handled in the constructor for PolicySet Bug: 3192973 Change-Id: I060b17401c58498d1597c9322be588020deca69c
This commit is contained in:
parent
6926cf85ef
commit
ac05d5e179
@ -152,13 +152,9 @@ public class ProvisionParser extends Parser {
|
||||
tagIsSupported = false;
|
||||
}
|
||||
break;
|
||||
// Complex character setting is only used if we're in "strong" (alphanumeric) mode
|
||||
// Complex characters are supported
|
||||
case Tags.PROVISION_MIN_DEVICE_PASSWORD_COMPLEX_CHARS:
|
||||
passwordComplexChars = getValueInt();
|
||||
if ((passwordMode != PolicySet.PASSWORD_MODE_STRONG) &&
|
||||
(passwordComplexChars > 0)) {
|
||||
tagIsSupported = false;
|
||||
}
|
||||
break;
|
||||
// The following policies are moot; they allow functionality that we don't support
|
||||
case Tags.PROVISION_ALLOW_DESKTOP_SYNC:
|
||||
|
Loading…
Reference in New Issue
Block a user