Take Your Search Game to the Next Level with Dropbox Dash 🚀✨ Curious how it works? Ask us here!
Forum Discussion
Greg-DB
Dropbox Staff
Dropbox StaffReminder: The Dropbox API will no longer accept TLS 1.0 or 1.1
Beginning on or after April 13, the Dropbox API will require that calls use TLS 1.2 or greater. Traffic using TLS 1.0 or 1.1 will be rejected.
The latest Dropbox SDKs will select TLS 1.2 when a...
Greg-DBDropbox Staff
Dropbox StaffMark R.5 Thanks for the feedback. To clarify, I was not indicating that one would be required to update to an Objective-C SDK from late 2020. Rather, I was responding to Robert's specific question and confirming that such as version should be sufficient. I don't have specific versions of the Objective-C and .NET SDK to note. The system should automatically use the latest available version. The Java and Python SDKs were only called out in particular since those were more recent and contained code that would affect the version used. If you need help confirming anything for your app(s) in particular, please open an API ticket.
Even without a specific test for use of the deprecated protocols, there is one thing Dropbox could do to help us know if we have a problem with our latest version. In the e-mail that goes out to developers telling them that they detected "some activity" with the deprecated protocols, why not include something more quantitative? Tell us, for instance, the percentage of deprecated uses. If our current versions are indeed faulty, then 100% of the accesses will involve the deprecated protocols. But if only 7% of the accesses are problematic, then we can rest easy knowing that the 7% must represent users who have not updated their apps. Dropbox has the data, right?
- Greg-DB
Robert S.138 Thanks for the feedback/idea! I can't make any promises myself, but feel free to open an API ticket if you'd like to request specific help/information.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
