Log errors in verifyChallengeInternal()

It is unexpected for verifyChallengeInternal() to fail, since the
Gatekeeper enrollment of the synthetic password (more specifically, the
Gatekeeper password derived from the synthetic password) should always
be valid.  Therefore, ensure that an error message is logged in all
failure cases.

Bug: 282947979
Change-Id: Ic8d0134bc4f3e0979bf500ffb5a99f2522251d39
Merged-In: Ic8d0134bc4f3e0979bf500ffb5a99f2522251d39
(cherry picked from commit b60583c3b1)
This commit is contained in:
Eric Biggers
2023-05-22 17:41:04 +00:00
parent d3252e4e76
commit aa19b22208

View File

@@ -1327,8 +1327,10 @@ public class SyntheticPasswordManager {
}
return result;
} else if (responseCode == GateKeeperResponse.RESPONSE_RETRY) {
Slog.e(TAG, "Gatekeeper verification of synthetic password failed with RESPONSE_RETRY");
return VerifyCredentialResponse.fromTimeout(response.getTimeout());
} else {
Slog.e(TAG, "Gatekeeper verification of synthetic password failed with RESPONSE_ERROR");
return VerifyCredentialResponse.ERROR;
}
}