AV | Posts: 36

Does the SDK version used have to be updated with each OneSpan major verson

0 votes

Hi,

 

When OneSpan releases a new version on their production environment, will there will always a corresponding SDK version update as well? How are the OneSpan environment and SDK updates timed?

Can the integration code use an earlier version of SDK even when the OneSpan environment has been updated to a new major version? 

What is the recommendation from OneSpan on these major releases and SDK versions update ?

 

Thanks


Duo_Liang | Posts: 3776

Reply to: Does the SDK version used have to be updated with each OneSpan major verson

1 votes

Hi Anu,

 

For this question "Can the integration code use an earlier version of SDK even when the OneSpan environment has been updated to a new major version?"

Normally you don't need to update your SDK every time when OneSpan Sign has a new release, because the SDK itself is designed and tested Forward Compatible to the latest API service. On the other side, API schema very seldomly get changed, or changed in a way that compatible to the SDK modelling.

For example, you may have noticed that at package JSON, there are some attributes added recently, like "conditions" for conditional field feature, "retainUntil" for the data retention management, but these won't affect the normal use of older SDKs that don't include these functions.

 

"When OneSpan releases a new version on their production environment, will there will always a corresponding SDK version update as well? How are the OneSpan environment and SDK updates timed?"

 

Theoratically there's always a corresponding SDK along with the new product release unless there's no or few code changes.(Tags page for the new .NET SDK repository)

 

"What is the recommendation from OneSpan on these major releases and SDK versions update ?"

For new users, it's suggested to download the latest SDK; For on-premise users, it's suggested to download the same SDK version as their installation. But as the foregoing state, you don't necessary to update the SDK every release.

But you should consider to upgrade your SDK IF:

(1)a new feature only introduced since a certain version, then you may want to upgrade to the latest SDK version

(2)for .NET SDK in particular, there's a main upgrade recently that we've moved the project to a new repository, .NET standard 2.0 get supported, some classes and namespaces are rebranded from eSignLive to OneSpan, and the project is hosted back at Nuget. And we stopped updating the old repository since 11.33 version.

You can read my blog for more information. 

(3)although it's not expected, in case the new release breaks the SDK function, or there's a known issue in the older version SDK, you may need to upgrade as well.

 

Duo


AV | Posts: 36

Reply to:

0 votes

Thanks Duo. Your reply is very helpful.

 

Is .NET SDK 11.32 supported on prod version 11.35 & 11.36 ?

I haven't run into any issues on Sandbox running on v11.35 and .NET SDK version of 11.32. This is our first time integrating with OneSpan using .NET SDK.

Will the behaviour be same on prod?

Thanks.


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off