Simplify untrusted reset logic
Instead re-initializing the synthetic password, just call
setLockCredentialWithAuthTokenLocked similar to normal flow
since we have the cached auth token.
The existing synthetic password initializtaion flow actually
has a bug when an untrusted reset to clear password is invoked:
it wrongly assumes that it's in case 2 and creates a new SID for
the user, instead of clearing it. This leads to the CTS failure.
Test: On a FBE device, execute cts-tradefed run cts -m CtsDevicePolicyManagerTestCases
-t com.android.cts.devicepolicy.MixedDeviceOwnerTestApi25 and verify device unlocks
successfully after the reboot.
Bug: 72875989
Change-Id: I5939335a27b10528b772d193f1e1034fd79abb9b
1 file changed