Onescan

Dear Partner

 

Onescan service withdrawing support for TLS1.0 and SSL 3

Date: 17:00 GMT 3^rd November 2016

 

Ensygnia will be removing support for the TLS1.0 and SSL 3 protocols due to the security associated risks with these protocols. This will take place on the 3^rd November 2016 after 17:00 GMT and could affect your integration with our platform.

 

Most platforms and languages seek to use the latest protocol version available which for Onescan is TLS1.2 and therefore, you should not experience any problems with this transition. PHP, Java, Python and Ruby tests have all proved positive so far internally.

 

All Mobile SDK users should be unaffected but need to check their use of the APIs to initiate Onescan sessions and call backs.

 

The only exception so far noted is with some .NET implementations using the APIs that often default to TLS1.0 and will therefore fail to communicate with our platform as a result. The solution to this is simple and just requires the following adding to your code.

 

System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

 

This only needs to be set once so can be added during application start up. One thing to note however, is that this is a global setting and this could affect other web requests made by your application so please consider this in your testing.

 

If you experience any issues with your use of the platform then please contact us at support@ensygnia.net and we will help you to resolve as soon as possible.

 

Many thanks for your use of the Onescan platform and we apologise for any inconvenience this transition may cause, but as security is at the heart of everything what we do here, I am sure you will understand the importance of this change.

 

Best regards

Matt Deacon

CTO