fc06773c0a5e666a693a07c99a12d5ff60bd43fb - platform_frameworks_base

commit	fc06773c0a5e666a693a07c99a12d5ff60bd43fb	[log] [tgz]
author	Rubin Xu <rubinxu@google.com>	Mon Mar 18 11:01:18 2019 +0000
committer	Rubin Xu <rubinxu@google.com>	Mon Mar 18 17:27:24 2019 +0000
tree	3b82fa48b7cd3b5d120b2cdae2cf61f881968ffa
parent	bbe1969596ac122e87193ca9200ad8963ddc5b30 [diff]

Force LSKF in ConfirmCredential UI when pending escrow token exists

Escrow tokens can only be activated by user confirming their LSKF,
while ConfirmCredential allows both LSKF and biometrics by default.
By requiring LSKF, it simplifies the DPC's flow of requesting the user
to activate a pending escrow token.

This change introduces an internal API to query the existence of
pending escrow tokens.

Bug: 127377026
Bug: 76084679
Bug: 79547502
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/locksettings/
Change-Id: Ie1ae58d2639394a9e6e1bf13d8bde44dfea240e8

core/java/com/android/internal/widget/ILockSettings.aidl[diff]
core/java/com/android/internal/widget/LockPatternUtils.java[diff]
services/core/java/com/android/server/locksettings/LockSettingsService.java[diff]
services/core/java/com/android/server/locksettings/SyntheticPasswordManager.java[diff]
services/tests/servicestests/src/com/android/server/locksettings/SyntheticPasswordTests.java[diff]

5 files changed