Integrate the OneSpan Device Binding SDK

This procedure allows you to integrate and use the OneSpan Device Binding SDK in your Android project.

To use the OneSpan Device Binding SDK in your Android project

1. Link DeviceBindingSDK.aar from the OneSpan Mobile Security Suite package to the aars folder.

2. Link UtilitiesSDK.aar from the OneSpan Mobile Security Suite package to your project.

3. Add the Kotlin dependency to your gradle build script:

   dependencies {
   implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.6.0"
   }

Prior to Android 10, you need to set the READ_PHONE_STATE permission in the AndroidManifest.xml file of your application if the Serial is used with the fingerprint method

For applications that target API 23 (or later) and run on Android 6.0 (or later), the READ_PHONE_STATE permission must be explicitly requested at runtime. See the Android sample in the OneSpan Mobile Security Suite package for more details.

To prevent the backup of the data file the Device Binding SDK created, including a full system backup where all application data are saved via adb, you must edit the application manifest file and set the attribute android:allowBackup to false.

You are now ready to use the Device Binding SDK. For more information on the methods, see Obtain the device fingerprint.

This procedure enables you to integrate and use the OneSpan Device Binding SDK in your iOS project.

To use the OneSpan Device Binding SDK in your iOS project

• Link MSSDeviceBinding.xcframework from the OneSpanMobile Security Suite package to your Xcode project.

• If you need to share your unique device identifier between several of your own applications, you must configure your project and use the proper access group when calling the API.

To learn more about how to share fingerprints using different kinds of access groups, open the MSSDeviceBinding.doccarchive file from the iOS/Documentation folder of the package and consult the tutorials.

To see the Objective-C error codes mapped to Swift error cases, refer to the DeviceBindingErrorCodes enum in the SDK's public header MSSDeviceBinding-Swift.h.

To ensure data privacy during the SDK integration, depending on your integration, you may have to add a privacy file to your application.

If you are using the Device Binding SDK with MSSCDDC or MSSDigipass, you must indicate that the device ID is recorded in your app's PrivacyInfo.xcprivacy file. Do this by adjusting the following settings:

• If you are using the Device Binding SDK with MSSCDDC SDK, NSPrivacyCollectedDataTypeTracking must be set to true.

• If you are using the Device Binding SDK with MSSDigipass SDK, NSPrivacyCollectedDataTypeLinked must be set to true.