- 05 May 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Overview of the Orchestration SDK
- Updated on 05 May 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
The SDK consists of a client component. This component interprets the orchestration commands and executes them in a mobile application, fully hiding the complexity of the secure features’ integration. The encoding and decoding of the orchestration commands is transparent to the mobile application.
Orchestration example – remote authentication overview illustrates an example of orchestration. It provides an overview of the Remote Authentication feature. If there is a risk for a given login request (e.g. unknown computer), the OneSpan Trusted Identity platform (TID) can dynamically request a step-up authentication on the mobile application using an authentication method (e.g. biometric recognition) that has been previously defined for that type of risk.
Orchestration example – remote authentication overview
Supported platforms and requirements
The Orchestration SDK supports the following platforms for an integration in a mobile application:
Android devices:
Minimum Android 7 (API level 24)
Target Android 15 (API level 35)
iOS devices:
iOS 15 and later
Swift 5 and later
Xcode 16 and later
Version support
For information about the Orchestration SDK versions that are supported by OneSpan Intelligent Adaptive Authentication and OneSpan Cloud Authentication, refer to Intelligent Adaptive Authentication Release Notes and OneSpan Cloud Authentication Release Notes, respectively.
For more information about the Orchestration SDK features and functionalities, refer to Features of the Orchestration SDK.