Fix allowDeviceAuthentication failing on Android 31 and later
#225
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
non-biometric authentication. There is an issue in newer versions of Android that require different configuration of the biometrics library for dual auth flows.
a few other refactors to clean things up.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes are to attempt to address the issue outlined in #181. I was able to address the root issue where the
android.security.KeyStoreException: Key user not authenticatedis reported when attempting to sign with the private key. It appears from this documentation that when usingBiometricPrompt.authenticatewe must use the form of the method that does not takeCryptoObjectas that implies the prompt will be used for Biometric authentication only (supporting documentation https://developer.android.com/training/sign-in/biometric-auth#biometric-or-lock-screen).After updating the implementation to not use the
CryptoObjectform ofBiometricPrompt.authenticate. After enabling this new form of authentication for both Biometric and device authentication I did find that I was no longer able to verify the signature with my test backend. I was not able to resolve this issue and was hoping that someone else might take a look at my changes and be able to see what change may have caused this regression.