Migration V1 to V2

For using API v2 from .NET, we recommend using the official Dropbox .NET SDK:

 

https://www.dropbox.com/developers/documentation/dotnet

 

The examples show how to handle authorization, e.g., using DropboxOAuth2Helper in SimpleBlogDemo:

 

https://github.com/dropbox/dropbox-sdk-dotnet/blob/master/Examples/SimpleBlogDemo/Controllers/HomeController.cs#L176

I had a look at all docus but I cant recognize in the example how I can get an accesstoken. I can generate the uri to show the authentification to the user but I cant receive a token.

Can you gibe me a hint?

The access token is retrieved a few lines later when the user is redirected back to the app after authorizing it here:

https://github.com/dropbox/dropbox-sdk-dotnet/blob/master/Examples/SimpleBlogDemo/Controllers/HomeController.cs#L197

I unterstand the following Workflow of this example...

I get the Uri To Show the User the authorisation Website. With the Parameter 'code' the User must Input the code manually into my app.
Is this right ?

If you use the "code" flow without a redirect URI, then yes, the user will have to manually copy and paste the authorization code into the app.

Using a redirect URI is recommended though, as shown in the example, as that will automatically pass the authorization code to your app, without the user copying/pasting it manually.

OK, I understand this. Thanx

 

Unfortunately my next question... ;-)

 

Which format must the redirected uri be have? I must register this uri in the apps profile at dropbox. How can it be variable if my app runs on many different PCs?

As a security feature, each exact redirect URI does need to be pre-registered.

If you don't know the redirect URI ahead of time, one thing you may be able to do instead is to use one static redirect URI but encode the necessary information in the 'state' parameter, and decode it as necessary after the redirect back to your app, to handle it as necessary:

https://www.dropbox.com/developers/documentation/http/documentation#authorization

Alternatively, you could forgo using a redirect URI entirely. With the "code" flow, you can omit redirect_uri and have the user copy and paste the code manually. (Or, for the "token" flow, you can use https://www.dropbox.com/1/oauth2/display_token as the redirect URI and have the user copy and paste the access token.)

A static redirect URI? What could this be? I think I must use a format like "https:\\aWebSide.com\anything" but this side doesnt exist and dropbox will send the users browser to them.

 

With ApiV1 the user connect to dropbox and my app get the token to download anything to dropbox. This isnt a web app.

 

 

I see this code in an example

 

                var builder = new UriBuilder(
                    Uri.UriSchemeHttps,
                    this.Request.Url.Host);

                builder.Path = "/Home/Auth";

                return builder.ToString();

But this generates no static Uri. How can I register this kind of redirectUri in the my dropbox app profile?

A "static redirect URI" would just be some unchanging URL that you could rely on, as a place to send your users. You don't necessarily need to use that technique, but if you do you should only use a URI that you trust (ideally something you control) and that you sure will continue being available.

 

The example I linked to is built as a web app though, where the redirect URI would be just be a URL for the app.

 

Since it sounds like you're not building a web app, that doesn't apply here. In that case, the SimpleTest or UniversalDemo samples would be a better reference for you. Check those out to see how this can be handled in a client-side application.