Overview of the Device Binding SDK
- 03 Dec 2024
- 1 Minute to read
- DarkLight
- PDF
Overview of the Device Binding SDK
- Updated on 03 Dec 2024
- 1 Minute to read
- DarkLight
- PDF
Article summary
The Device Binding SDK generates a unique identifier, called Device fingerprint, for mobile devices using a 64-character hexadecimal string. This identifier is a SHA 256 hash of device-specific data and salts provided by integrators. Different salts should be used for different purposes. The SDK supports Android devices with minimum Android 7 and iOS devices with iOS 14 or higher. The package includes MSSDeviceBinding.xcframework for iOS and DeviceBindingSDK.aar for Android. Integration instructions have changed for Android and iOS in OneSpan Mobile Security Suite 4.20.0.
Did you find this summary helpful?
Thank you for your feedback
With the Device Binding SDK, a unique identifier for a given mobile device can be generated. This unique identifier, called Device fingerprint in the API, is a hexadecimal string of 64 characters. It is a securely computed SHA-256 hash of the device-specific data and salts.
As an integrator, you must provide a salt which will be used to diversify the generation of the device fingerprint.
Different salts must be used, if the device fingerprint is used for different purposes (e.g. one salt to protect a storage and another to protect a Digipass instance).
The Device Binding SDK supports the following platforms:
Android devices:
Minimum Android 7 (API level 24)
Target Android 14 (API level 34)
iOS devices:
iOS 14 or higher
Swift 5.0 or higher
Xcode 15 or higher
The Device Binding SDK package includes the following:
MSSDeviceBinding.xcframework for iOS
DeviceBindingSDK.aar for Android
As of OneSpan Mobile Security Suite 4.20.0, the integration of the Device Binding SDK has changed for Android and iOS. For instructions on how to integrate the SDK, see Integrate the Device Binding SDK.
Was this article helpful?