diff options
| author | Esteban Talavera <etalavera@google.com> | 2016-02-11 15:45:30 +0000 |
|---|---|---|
| committer | Esteban Talavera <etalavera@google.com> | 2016-02-11 15:45:30 +0000 |
| commit | 2547071ff8d83dc51c915a56202081ca3a100b23 (patch) | |
| tree | 2ef94f7bfe18094bf00a26aa29d5b0ae8004ac93 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | e64f3da729ae6a00fb627f00b8a97e7c5feb8bcb (diff) | |
Let admin disable fingerprint for the work challenge
Also, reworked the logic a bit:
* Admins can only set flags that affect the parent on the
parent DPM instance (i.e. no unredacted notifications)
* Admins can set flags not supported on the work challenge on
the regular DPM instance. If there is a work challenge,
they will have no effect (as managed profile policies don't
affect the regular lockscreen if there is a work challenge).
If there is no work challenge, they'll affect the parent profile.
Bug: 26891832
Change-Id: I8978e1aa6abe9c8dc07e030dfd069b5f4e1301f6
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions