As a part of our continued efforts to maintain the highest security standards on the DNAnexus Platform, we will deprecate support of TLS 1.0 and TLS 1.1 on October 15th, 2017. We have been communicating this proposed change, and most of the customers and users have upgraded.
If you are a user that still has programs or processes using TLS 1.0 or 1.1 when interfacing with the DNAnexus Platform you will need to take a few simple steps to upgrade. Please follow the instructions below to upgrade to TLS 1.2.
What is TLS?
TLS stands for “Transport Layer Security” and is a protocol that ensures connections made to a remote endpoint are the intended destination through encryption and endpoint identity verification. DNAnexus web and API connections use TLS as a key security component, thus it is important that the latest version of TLS is supported.
What do I need to do?
For macOS/OS X Users:
If you are using the DNAnexus Platform SDK (a.k.a. dx-toolkit) with the Python version provided with your operating system, you will need to install an alternative Python version with TLS 1.2 support. We suggest using the Homebrew package manager to install Python version 2.7.13:
Install Homebrew using the instructions at https://brew.sh/.
Once Homebrew is installed, run the following command in your terminal prompt:
brew install python
Once the Python version is installed follow the instructions at https://wiki.dnanexus.com/Downloads to download, unpack, and activate the latest dx-toolkit release.
For Internet Explorer Web Browser Users:
If you use Internet Explorer version 10 or earlier, you will need to upgrade your web browser to Internet Explorer 11 or later.
For All Other Users:
If you use a PC, or if your web browser is Internet Explorer 11 or later, Chrome, Firefox, or Safari, we do not expect that your access to DNAnexus will be impacted by this upgrade.
If you are impacted, please make the necessary modifications by October 15th, 2017 in order to maintain continued access to DNAnexus. Please do not hesitate to contact email@example.com with any questions or concerns.