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

Commit ef6c53ba authored by Grace Cheng's avatar Grace Cheng
Browse files

Secure lock device implementation for legacy keyguard

KeyguardSecurityContainerController updates: does not dismiss after
successful primary auth, updates keyguard view shown for primary ->
biometric authentication transition, biometric -> lockscreen transition,
biometric -> gone transition

StatusBarKeyguardViewManager updates: resets keyguard and hides bouncer
on secure lock device biometric auth interruption, notifies
PrimaryBouncerInteractor and KeyguardDismissTransitionInteractor when
secure lock device is fully unlocked & ready to dismiss, notifies
SecureLockDeviceInteractor when gone transition finishes, and does not
notify PrimaryBouncerInteractor on biometric authentication (this is
handled by KeyguardBouncerViewBinder)

Updates KeyguardSecurityViewFlipperController to return the new view for
the SecureLockDeviceBiometricAuth security mode

Updates KeyguardSecurityModel to return
SecurityMode.SecureLockDeviceBiometricAuth when secure lock device
biometric authentication is being shown or pending dismissal

Updates SecureLockDeviceInteractor to track unlock progress during
secure lock device, and reset UI state, auth flags, and face auth
request status in response to biometric auth being requested,
interrupted, or completed

Updates KeyguardService to not re-enable keyguard after secure lock
device unlock is complete

Updates KeyguardBouncerViewModel/ViewBinder to handle showing and hiding
the biometric authentication view on biometric authentication requested,
interrrupted, and completion

Flag: android.security.secure_lock_device
Bug: 401645997
Fixes: 427071518
Test: atest KeyguardSecurityContainerControllerTest
Test: atest KeyguardBouncerViewModelTest
Test: atest StatusBarKeyguardViewManagerTest
Change-Id: Ia4375434b09efc68c5502e6008462d784ace7596
parent 6a7309a3
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