Dot Net SDK provided by Dropbox is not updated with TLS 1.2

[naveedsw]

I AM TRYING TO UPDATE MY APP FROM TLS 1.0 TO TLS 1.2 AND POOR SUPPORT IS AVAILABLE AND REALLY UPSET.

ONLY JAVA AND PYTHON UPSTED SDK AVAILABLE.

[Greg-DB]

The Dropbox .NET SDK is already automatically uses the best available version of TLS, though we recommend updating to the latest version of SDK in general as a best practice, if you haven't already. The latest version of the Dropbox .NET SDK is currently v6.26.0.
 
While the Dropbox SDK itself will use the best available TLS protocol version, this will also depend on what TLS protocol version your platform itself supports. You'll need to make sure your platform has support for TLS v1.2 enabled.
 
For your client/environment, please refer to the relevant documentation for information on enabling the relevant platform support. For example, Microsoft in particular appears to have some resources here which may be helpful:
 

• https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls
• https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client

[naveedsw]

I need very simple console sdk which can upload file into dropbox. I am using desktop application i dont where to get url?
Or if you have step by step guide line

[naveedsw]

I need very simple console sdk which can upload file into dropbox. I am using desktop application i dont have url?
Or if you have step by step tutorial for tls 1.2

[naveedsw]

i think i am wasting my time here drobox is a simple platform and now its a HELL. i think i have search some other service. how can i refund my payment.

[Greg-DB]

Dropbox offers the official Dropbox API v2 .NET SDK here: https://github.com/dropbox/dropbox-sdk-dotnet

There are instructions for that here: https://github.com/dropbox/dropbox-sdk-dotnet#readme

And examples here: https://github.com/dropbox/dropbox-sdk-dotnet/tree/main/dropbox-sdk-dotnet/Examples

For instance, this example includes code for uploading files: https://github.com/dropbox/dropbox-sdk-dotnet/blob/main/dropbox-sdk-dotnet/Examples/SimpleTest/Progr...

That can be used both client-side (such as in desktop apps) as well as server-side. That may not be as simple as you're looking for though, as it offers a substantial amount of functionality for using the entire Dropbox API for a number of different scenarios. Dropbox does not offer a different or simpler .NET SDK than that.

Anyway, this is the forum for API questions, but if you have any account/payments questions, you can contact the relevant support department here: https://www.dropbox.com/support/

[naveedsw]

hi,

Can anyone tell me what is "authorize" value here and "token" in provided SDK

// URL to receive OAuth 2 redirect from Dropbox server.
// You also need to register this redirect URL on https://www.dropbox.com/developers/apps.
private readonly Uri RedirectUri = new Uri(LoopbackHost + "authorize");

// URL to receive access token from JS.
private readonly Uri JSRedirectUri = new Uri(LoopbackHost + "token");

[Greg-DB]

In the code snippet you shared, "authorize" and "token" are just strings used as URL paths on the local server used to handle the result of the OAuth app authorization in that example app.

[naveedsw]

Thanks for your reply. do you have any video tutorial which can explain the tutorial comments written with this SDK is not enough to understand for me. i am sorry i am taking your time but i am really helpless, please convey my message to developer team currently i am trying to switch google drive and i found hundreds of videos available on web. dropbox have some old SDK's which they copy past against each post or problem. we know that dropbox totally change the idea from simple TLS 1.1 to TLS 1.2 but 3 years old SDK are not enough they should make videos and more sdks as well.

know you can help me to understand the following url purpose and where i get it from.

 private const string LoopbackHost = "http://127.0.0.1:52475/";  

[Greg-DB]

We don't have video tutorials for the API/SDKs, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though.

The "LoopbackHost" in the example is the address of a local server, defined by the app, used for the redirect URI for the OAuth app authorization flow. That's where the app receives the result of the app authorization step to complete the flow.