diff options
| author | Pavel Grafov <pgrafov@google.com> | 2021-03-05 09:44:44 +0000 |
|---|---|---|
| committer | Pavel Grafov <pgrafov@google.com> | 2021-03-24 23:16:09 +0000 |
| commit | bca12f4774705eb9b5d7de39ef0675e0fba89ac1 (patch) | |
| tree | ee9e07d0f7cdbb69faeaa0b7d7a1b657601d2bdb /rs/java/android/renderscript/ProgramVertexFixedFunction.java | |
| parent | 30c71e6288926fdfdcfea37bc8de543353dd2ca4 (diff) | |
Allow COPE DPC to confirm compliance explicitly
Currently when COPE PO sets a maximum managed profile time off
policy, it is sufficient for the user to turn the profile on
briefly to reset the timer, which technically allows the user
to circumvent the policy, doing so repeatedly.
With this change DPC can control when the timer gets reset by
acknowledging compliance explicitly.
By default, the behavior is the same as before unless the DPC
overrides DAR#onComplianceAcknowledgementRequired in which case
it will have to call DPM.acknowledgeDeviceCompliant when the
timer can be safely reset, e.g. after a successful policy sync.
Bug: 181943978
Test: atest OrgOwnedProfileOwnerTest#testWorkProfileMaximumTimeOff_complianceRequiredBroadcastDefault
Test: atest OrgOwnedProfileOwnerTest#testWorkProfileMaximumTimeOff_complianceRequiredBroadcastOverride
Test: atest OrgOwnedProfileOwnerTest#testWorkProfileMaximumTimeOff
Test: atest com.android.server.devicepolicy.DevicePolicyManagerTest
Change-Id: I6efea53aad8097c047f1e3ebf62b421dc32214e6
Diffstat (limited to 'rs/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions