tree 5881e5beb7a47aa9ced20b48fa27aada76109ce4
parent f98e1086f5a039d98becf7203367b663e72d09f5
author Rubin Xu <rubinxu@google.com> 1572948936 +0000
committer android-build-team Robot <android-build-team-robot@google.com> 1584593511 +0000

RESTRICT AUTOMERGE
Update keyguard locked state from TrustManagerService

TrustManagerService holds the ground truth about whether a user is
locked or not, so update keystore using the information there,
instead of doing it from KeyguardStateMonitor. This fixes the issue
of work profile locked state not being correctly pushed to keystore.

Note: since this change is likely to be backported as a security
patch, I'm refraining from doing major refactoring right now.

Bug: 141329041
Bug: 144430870
Test: manually with KeyPairSampleApp
Change-Id: I3472ece73d573a775345ebcceeeb2cc460374c9b
(cherry picked from commit f9418dbb2c2469dd271e4aebefda5b6a4b485f3a)