Store biometry key for each PowerAuthSDK instance (1.7.x) #626
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
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.
This PR modifies how the
PowerAuthSDKclass on Android internally stores biometry-related encryption keys. In previous versions, the key was shared between multiplePowerAuthSDKinstances. Now, the shared key is only used if the activation has already configured a biometric factor. Once the factor using the shared key is removed, or the entire activation is removed, a per-instance key will be created during the next biometric setup.This backward compatibility feature can be disabled in the
PowerAuthKeychainConfigurationif required by the application. For instance, if the application uses multiple instances ofPowerAuthSDK, it is important to disable this feature to ensure the shared key is immediately forgotten.Other changes: