An update to our AssureSign Solution for CRM has been posted here. This version of the AssureSign solution provides a critical change to address the end of support for the TLS 1.0 and 1.1 encryption protocols (announced here). The end of support was announced for an earlier date, but in order to allow for some client applications to be migrated gracefuly we have extended the period to a later time. AssureSign will be providing an exact date for making the change to disable TLS 1.0 and 1.1 in the coming weeks, but the new targeted cutover will likely be sometime in February.
These encryption protocols used to secure web communications are being decremented in order to allow us to use the latest, more secure TLS 1.2 protocol. The CRM solution update is required to ensure API communications made to our SaaS AssureSign instances from the plugin code will continue to work properly after support for the older protocols is turned off. If you are currently using the CRM solution to communicate to an on-premise installation of AssureSign, then this update is not currently required.
The latest available managed solution version is 220.127.116.11. CRM online customers should install the version for CRM 7.1.
On-Premise installations should apply the appropriate solution for the version of CRM installed:
|18.104.22.168||Before CRM 2013 and Microsoft Dynamics CRM Online Fall '13|
|22.214.171.124||CRM 2013 and Microsoft Dynamics CRM Online Fall '13|
|126.96.36.199||Microsoft Dynamics CRM 2013 Service Pack 1 (SP1) and CRM Online Spring '14|
|188.8.131.52||Microsoft Dynamics CRM 2015 and Microsoft Dynamics CRM Online 2015 Update|
|184.108.40.206||Microsoft Dynamics CRM Online 2015 Update 1|
If you have any questions regarding this CRM solution update, please contact us at email@example.com.