Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content
Commit c6597405 authored by Sarup Dalwani's avatar Sarup Dalwani
Browse files

Adding Access Control in CrossProfileIntentFilter

Adding field to manage access control on CrossProfileIntentFilter. It
can have 3 values(as of now) (1) ALL, which means any user can
add/modify/remove CrossProfileIntentFilter (2)SYSTEM, which means only
system can add/modify/remove CrossProfileIntentFilter and (3)
SYSTEM_ADD_ONLY,
which means only system can add but no user can modify/remove. The
default would be ALL to ensure there is no impact on OEM/3P
DevicePolicyControllers configuring work profile.The default for clone
profile would be SYSTEM, so that no OEM/3P can add or remove
CrossProfileIntentFilter which may lead to unexpected behaviour for app
cloning.

Bug: 238019465
Test: tested this by flashing the device along with intent redirection
code. Tested adding CrossProfileIntentFilters for owner, work and clone
profile.
Design Document: go/intent-redirection-blue-doc

Change-Id: I3e6c3dcb5d822add9892515a7138def4958cfeb2
parent 2667ba46
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment