summaryrefslogtreecommitdiff
path: root/keystore/java/android/security/KeyChain.java
diff options
context:
space:
mode:
authorPhilip P. Moltmann <moltmann@google.com>2019-02-08 13:07:57 -0800
committerPhilip P. Moltmann <moltmann@google.com>2019-02-16 12:11:38 -0800
commitcfd2fbc4e3223afd79ed32fdfbdf09fa7ddfa43b (patch)
tree27f1e2a57caeba35bf4030a371323a75be3fd413 /keystore/java/android/security/KeyChain.java
parent0d05e48371c67ce0e95faf0915e96b97361770f5 (diff)
Make PermissionControllerManager user aware
Most of the commands of PermissionControllerManager should go to the calling user. If not - and the alternate user is running - we should use the recommended way to talk to alternate users. This recommended way is to create a package context for the user and call the method on this new context. Hence - At a time we can have more than one RemoteService (one per user) - Connect to the user declared in Context#getUser instead of the calling user Test: Called methods on work-profiles and saw alternate PermissionController apps to be spawned. Change-Id: I9ed87db1f658f18b69d19b39ba9f96361ec5af82
Diffstat (limited to 'keystore/java/android/security/KeyChain.java')
0 files changed, 0 insertions, 0 deletions