Additional considerations for Android

Migrations

We only support migration from an older version to a newer version of the SDK. If you need to run test scenarios with an older version, it is mandatory that you clear all fingerprints before running those test scenarios.

Fingerprints

Generate fingerprints when HARDWARE parameter cannot be used

We primarily recommend using the HARDWARE parameter to generate the device fingerprint except when the Device Binding SDK is not able to generate the fingerprint.

For example, there are known issues with:

• devices with Mediatek Chipset MT6737 (and variants) running Android 7

• Xiaomi Redmi Note 8 Pro devices running Android 11

In these cases, the SDK terminates unexpectedly while attempting to generate the fingerprint. As an exception, when the HARDWARE parameter cannot be used, we recommend using the ANDROID_ID option as a fallback mechanism.

Fallback mechanism for StrongBoxUnavailableException

A known issue exists that is related to StrongBoxUnavailableException.

Please note that this is not an issue of our SDKs but is caused on the manufacturer's side and outside the control of OneSpan. There is the possibility that this may be fixed automatically in the future.

To provide a fallback mechanism, we have added a new error code, STRONGBOX_UNAVAILABLE and a new fingerprint type, HARDWARE_WITH_TEE.

The recommended flow to generate the fingerprint is the following:

1. Call the APIs as before by creating the instance using HARDWARE as fingerprint type.

   DeviceBinding.createDeviceBinding(context, FingerprintType.HARDWARE).fingerprint(SALT) 

2. If this API returns an exception with the error code STRONGBOX_UNAVAILABLE create a new instance with the new fingerprint type HARDWARE_WITH_TEE:

   DeviceBinding.createDeviceBinding(context, FingerprintType.HARDWARE_WITH_TEE).fingerprint(SALT)

   The use of TEE can result in a different fingerprint being generated.

Shared functionalities of the Device Binding SDK and other Device Binding SDK SDKs

The following features are included in the Device Binding SDK but a better practice is to integrate them with other Device Binding SDK SDKs

• New activations using the fingerprint method

  For more information, refer to the Digipass SDK Integration Guide.

• Managing the fingerprint as the unique identifier for the device

  For more information, refer to the Client Device Data Collector SDK Integration Guide.