commit 45927898c7c46462298f7e2cd6ac1e28b9f86dda
author Pavel Grafov <pgrafov@google.com> Wed Aug 15 21:07:01 2018 +0100
committer Pavel Grafov <pgrafov@google.com> Fri Aug 17 22:07:12 2018 +0000
tree cb766ced5a59008995bea0ef3ead205ab5f7371c
parent 6fdf8c225d8bae3455499744cafaf626760b8076

Don't offer "None" lock type for work profiles.

"None" doesn't make sense for work profiles because it makes
profile insecure even if primary user is secure. If the user
wants to get rid of separate challenge, it will be offered in
previous Settings page, "Use one lock", so this shouldn't cause
any confusion.

Test: atest tests/robotests/src/com/android/settings/password/ChooseLockGenericControllerTest.java
Test: manual, tried setting personal an work challenges from Settings and via Intent.
Bug: 33656033
Change-Id: I830b3e372c1fe200fc4e02d59e3c3805bac5f9bb