Non-breaking change.
When will this feature be available?
This feature is already available to Futurae Android and iOS SDKs customers that integrate the SDKs version 2.1.0 and beyond.
What is this feature about?
We are thrilled to introduce a significant enhancement to our Futurae mobile SDKs: SDK PIN for Automatic Account Recovery. This new feature adds an additional layer of security and convenience to Automatic Account Recovery, and plays a crucial role in protecting user accounts, preventing unauthorized access, and enhancing the overall security of the Futurae mobile SDKs.
How does it work?
1- If the accounts to be recovered were originally enrolled with an SDK PIN or later switched to an SDK PIN configuration, users will be prompted to enter the SDK PIN that was configured on the previous SDK, before recovering their enrolled accounts. This step ensures a secure account migration process and prevents unauthorized access. By confirming the SDK PIN during account recovery, users can maintain the same level of security they had previously established.
2- In cases where the accounts to be recovered were not protected by an SDK PIN, and the current lock configuration type is LockConfigurationTypeSDKPinWithBiometricsOptional
, users need to set a new SDK PIN during the account migration process. This empowers users to establish a new, secure PIN for their accounts and can enhance the protection of their accounts during the account recovery process.
How to integrate this feature?
To use this feature it’s necessary to update the Android and iOS SDK versions to v2.1.0 or higher. Please refer to the following releases:
After updating the SDK version, the instructions to use the SDK PIN feature during Automatic Account Recovery are described in the below documentation:
Android SDK Automatic Account Recovery
iOS SDK Automatic Account Recovery
Does this change have any impact on my Futurae SDK integration?
If the SDK was initialized with the lock configuration type SDKPinWithBiometricsOptional
, the executeAccountMigrationWithSDKPin
method should be implemented and called in the following scenarios:
1- If the user had a previous SDK PIN, they need to enter it to confirm the account migration. The entered SDK PIN should be provided as an argument to the above method.
2- If the accounts to be recovered were not protected by an SDK PIN and the current SDK lock configuration is LockConfigurationTypeSDKPinWithBiometricsOptional
, the provided SDK PIN will serve as the new PIN for unlocking the SDK, and this same PIN will be required for further account recovery attempts for the specific user.
For any questions please contact our support at support@futurae.com.
Comments
0 comments
Article is closed for comments.