The following sections can help you to get started with OneSpan Sign's SDKs:
- SSL Communication
- Integration Environment
- OneSpan Sign Java SDKs
- OneSpan Sign .NET SDKs
- OneSpan Sign Mobile SDKs
- OneSpan Sign APEX SDK
Integration with OneSpan Sign is secured via an SSL certificate issued by GlobalSign. Thus that GlobalSign intermediate certificate must be installed in your integration environment.
While you can add any of the certificates in the certificate chain, the Root-CA certificate should work for most environments.
In light of the Logjam security vulnerability, OneSpan Sign has increased its DH SSL key from 1024 bits to 2048 bits.
Older versions of Java and .NET will no longer be able to connect to OneSpan Sign, since they don't support the larger encryption key.
Certificate serial#: 04 00 00 00 00 01 21 58 53 08 a2 Thumbprint: d6 9b 56 11 48 f0 1c 77 c5 45 78 c1 09 26 df 5b 85 69 76 ad
Download link: https://secure.globalsign.net/cacert/Root-R3.crt
Our Java SDKs enable integration with any application written in the Java programming language.
Your JVM must be using Java 1.7.0_21 or higher.
To identify the Java version installed on your system, run the following command:
If you want to work with an OneSpan Sign Java SDK, download the 11 version.
To view Javadoc documentation for an OneSpan Sign Java SDK: (1) download the 11 version; (2) unzip the downloaded file; (3) run the file
The OneSpan Sign Java SDKs support Java 1.7_21 and higher.
For additional information, see the GitHub examples below.
To download the OneSpan Sign Java SDK, click here.
To see if this certificate is already installed in your environment, run the following command:
keytool -list -keystore <JAVA_HOME/lib/security/cacerts> | grep -i d6:9b:56:11:48:f0:1c:77:c5:45:78:c1:09:26:df:5b:85:69:76:ad
If the certificate is not installed, install it by running the following command:
keytool -importcert -alias GlobalSignRootCAR3 -keystore <JAVA_HOME/lib/security/cacerts> -file Root-R3.crt
Sample Java Code
If you are a Maven user, add to your pom file the appropriate one of following dependencies.
For SDK 11:
<dependency> <groupId>com.silanis.esl</groupId> <artifactId>sdk</artifactId> <version>11.18</version> </dependency>
If you want the version of the SDK that bundles all dependencies, add
<classifier>jar-with-dependencies</classifier> to the dependency.
If you are using Java to integrate, we recommend that you download and run our Diagnostics Application. That application checks the compatibility of your JVM with OneSpan Sign's SSL security settings.
You can download the Diagnostics Application here.
To run the Diagnostics Application:
- Ensure that you are on the Production JVM, or on a testing JVM that is identical to the Production JVM.
- Run the following command:
- If the test result is negative, an error message appears that begins: Your system is not compatible with eSignlive!
java -cp securityscanner.jar com.silanis.esl.Scanner
Our .NET SDKs enable integration with any application written in the C# programming language.
If you want to work with an OneSpan Sign .NET SDK, download the 11 version, and perform the extra configuration described below. For additional information, see the GitHub examples below.
We now support .NET Standard 2.0 and .NET framework 4.5 or higher. This means that .NET Core is also supported, and that Linux machines can also be used.
To identify the .NET framework installed on your system, follow the instructions in this link: https://msdn.microsoft.com/en-us/library/hh925568
To download the OneSpan Sign .NET SDK, click here.
To install the certificate, double-click the file
Root-R3.crt, and then select install certificate.
Sample .NET Code
Our Mobile SDKs enable integration with Web applications on mobile phones and tablets.
Which one applies to you depends on your Operating System:
- To learn how to download and integrate the iOS SDK, click here.
- To learn how to download and integrate the Android SDK, click here.
Written in APEX, the OneSpan Sign APEX SDK for Salesforce enables developers to integrate e-signing functionality into their custom apps on either Salesforce or the Force.com platform.