We previously announced an important change we will be making to address the end of support for the TLS 1.0 and 1.1 encryption protocols. These encryption protocols are used to secure web communications and are being deprecated in order to allow us to use the latest, more secure TLS 1.2 protocol. The end of support was originally announced for an earlier date (the 5.24 release), but we pushed the date back in order to allow extra for some client applications and implementations to be migrated gracefully to use TLS 1.2.
The new date for the end of support for TLS 1.0 and 1.1 is February 24th, 2015. Starting on this date, any client applications or implementations that rely on the older TLS 1.0 and 1.1 protocols will be unable to communicate with AssureSign SaaS environments. We recommend that all clients utilizing custom SSL proxies or custom integration from older server environments review their systems to ensure that they can communicate with AssureSign via the TLS 1.2 protocol.
In support of this change, we will be publishing new versions of certain AssureSign client applications that required modifications in order to be compatible with TLS 1.2. Any clients that currently make use of the following applications should plan on installing/deploying the new versions prior to February 24th, 2015. We'll separately provide notices once the new versions of the applications have been published and are available for download (expected within the next couple of weeks).
If you have any questions or concerns regarding these changes, please contact support via a new discussion or by sending an email to firstname.lastname@example.org