RSA announces the availability of RSA Mobile SDK 3.10. With this release, RSA provides new enhancements, certifications and fixed issues.
What's New in this Release
Removal of EyeVerify Eyeprint Authentication
The Mobile SDK Authentication Module no longer supports EyeVerify Eyeprint authentication. Customers who have implemented the EyeVerify Eyeprint ID within our SDK have support available until December 31, 2018. For more information, see the RSA Adaptive Authentication Step-Up Authentication Direction Update.
To continue using Eyeprint ID, customers can work directly with EyeVerify and leverage our MCF/FI defined authentication to integrate it with Adaptive Authentication.
RSA Mobile SDK Authentication Module continues to support device-embedded biometric authentication methods, such as native Android and iOS fingerprint authentication.
New iOS FaceID Authentication
The Mobile SDK Authentication Module supports FaceID authentication for the iPhone X. Customers can utilize iOS FaceID as a step up authentication method in Adaptive Authentication.
Enhanced Emulator and Compromised Device Detection
Enhanced emulator and compromised device detection packages and features are included in this version.
The Mobile SDK Data Collection Module leverages the Google SafetyNet Attestation API to detect if a device is compromised or emulated. You can now check if a device has been flagged as emulated or compromised by RSA legacy logic, with or without Google SafetyNet Attestation API.
The Mobile SDK Authentication and Data Collection Modules are certified for iOS 11 and iPhone 10.
Configurable Phone Number Hashing
In the Mobile SDK Data Collection Module, phone numbers can now be hashed for enhanced security.
Customers who use Adaptive Authentication (Hosted) or Adaptive Authentication (Cloud) with the Mobile SDK Data Collection Module must hash mobile numbers on the SDK side. Customers who use Adaptive Authentication (On-Premise) with the Mobile SDK Data Collection Module on the SDK side have the option of using the mobile numbers in clear text (the default configuration) or hashed.
In the Mobile SDK Authentication Module, the username is hashed for enhanced security if the customer uses RSA Push Notifications powered by Microsoft Azure Push Notification service.
Prompt for Permission Geolocation Collection
RSA Adaptive Authentication Mobile SDK Data Collection Module contains a new Prompt for Permission property for iOS. The Prompt for Permission property defines if a popup is displayed that requests location collection permission from the end-user when the customer performs collection in Mode 2. If the customer does not enable Prompt for Permission, the customer is responsible for obtaining the end-user permission for location collection.
Adaptive Authentication Push Notifications
In the Authentication Module, in order to use Adaptive Authentication Push Notifications, powered by Microsoft Azure Push notification service, for an optional authentication method, such as one-time-password, biometric and transaction signing, customers must use Mobile SDK Authentication Module version 3.10 or later, with RSA Adaptive Authentication 13.1 or later, or Adaptive Authentication (On-Premise) 7.3 P4 or later.
Register to download the product package and documentation from RSA Link at https://community.rsa.com/docs/DOC-41815.
For additional documentation, downloads, and more, visit the RSA Adaptive Authentication page on RSA Link.
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.