Actions
Bug #11178
openWhen disenrolling a device it doesn't send a policy revoke, policies are not revoked after disenroll
Start date:
09/08/2024
Due date:
13/08/2024 (about 3 months late)
% Done:
0%
Estimated time:
Device Type:
Component:
Type:
Android
Description
Environment details
Staging server (6.1.0)
Prerequisites
Enrolled device(COPE) with a policy applied on.
Steps
disenroll the device while the policy being applied.
can use the policy of restrictions -> Allow use of camera or disallow factory reset
Description
When the device disenrolled, a policy revoke operation should be send to device. but currently such operation is not send.
Hence after disenroll, the device still has the those policies applied.
Result
Policy bundle is still applied on the device even after disenrolled.
Updated by Sandaru Daminda 3 months ago
- Project changed from Backlog to product-uem 6.3.0 GA
- Assignee set to Kavin Prathaban
Updated by Sandaru Daminda 3 months ago
- Due date set to 13/08/2024
- Start date changed from 14/05/2024 to 09/08/2024
Updated by Rajitha Kumara about 1 month ago
- Project changed from product-uem 6.3.0 GA to product-uem 7.0.0 GA
Actions