| commit | da412f19d09e31fc3d82baf9a24b1c9ec16ac18c | [log] [tgz] |
|---|---|---|
| author | Eran Messeri <eranm@google.com> | Mon Jan 20 16:28:50 2020 +0000 |
| committer | Eran Messeri <eranm@google.com> | Tue Jan 21 16:55:09 2020 +0000 |
| tree | a452c0ade23908b87790d745093e047ef48f0129 | |
| parent | faa0e9dbca625f6c54c0ad0bc7d9f99ed42ba305 [diff] |
Clarify lockNow usage from a managed profile lockNow can be used by the profile owner of a managed profile both to lock all users and evict the encryption key of the managed profile. However, the order of calls is important. Document the order in which lockNow need to be called on the parent DevicePolicyManager instance so that the profile owner isn't stopped prior to locking all users. Bug: 148067606 Test: m docs Change-Id: I3e29e8cb02b74d41ef4f5d96467937149282cc07