End of Life - Inbound Connections using TLS 1.0 - Urgent

Follow

Created:
Updated:

In order to improve security, NetDocuments is dropping support for inbound connections using TLS 1.0 starting on May 17, 2017.  We had scheduled this for May 1, 2017, but we have adjusted the date to provide sufficient time for customers to make required changes. This provides that additional window of time for you to complete your upgrades. We have now scheduled to start on May 17, 2017 to make the change to ensure we maintain the utmost security for the Service. It will be done in phases at various entry points in our Service.  We anticipate that we will complete this process by the first week in June.  A few days prior to that date, we will provide an IP address for those that may still need to have an extended time. This will be provided for a limited time.

This is the final notice regarding the EOL. If you have not already done so, you should test your environment against our pool of servers where TLS 1.0 was previously disabled.  Refer to the IP addresses below.

The newer, more secure TLS 1.1 and TLS 1.2 protocols will continue to be supported. They are supported by all modern browsers and coding libraries.

However if you use any software to access the NetDocuments Service that has not been updated recently, you should check to ensure it supports TLS 1.1 or higher. 

Note that we previously dropped support for outbound connections using SSL 3.0 and TLS 1.0 as of the 17.1 Update on January 19, 2017.

Please make sure that you have the most current EMS Profiler and EMS Folder software installed prior to May 17 to avoid any issues. Also if you are using the ndLink product, you need to be using the 12/13/2016 version or later. You can find the latest versions of these products in the Downloads section in Help. Also, the Local Document Service software does not require any updates for the TLS change, however, you may be required to update the OS you are running on the server to ensure that it continues to work properly.

Prior to May 17, 2017, you can also use the following host file IP addresses to do testing to verify your software works alright.

192.100.0.174       vault.netvoyage.com        #tls 1.0 disabled

192.100.0.174       api.vault.netvoyage.com        #tls 1.0 disabled

192.100.0.174       upload.vault.netvoyage.com        #tls 1.0 disabled

192.100.0.174       ldserver.vault.netvoyage.com        #tls 1.0 disabled

Back to Top

Was this article helpful?
0 out of 0 found this helpful

Comments

Have more questions? Submit a request
Powered by Zendesk