Now that you have an Initial Access Token and Refresh Token, let’s configure our Spring Application: in the Access Token stands for Short-Lived token Spring Enter the authorization code here: Successfully requested scope account_info.read Authorization complete. Click 'Allow' (you might have to log in first).

The Oauth Flow will validate the Authorization and generate the Tokens for the Scopes asked.

This page will generate the Authorization Code and you must input this in Java Main program.

Create the authorize flow and prints the URL that you need to put in your browser to authorize Dropbox.

Use your App Key and Secret (you must add them in the Java Code) to initialize the Oauth Authorization Flow in Dropbox.

Now I will show how to implement, in Java and Spring, this new form of authorization. You should ensure your app works with short-lived access tokens.

You should review your apps permission tab to transition to scopes. For now, our App Console supports both legacy and scoped app creation, but may be turned off soon as we prepare to retire long-lived tokens on September 30th, 2021. The major changes to be aware of are the introduction of short-lived tokens, scopes, PKCE, and refresh tokens. You can read about them in the OAuth Guide or in the blog post, Now Available: Scoped Apps and Enhanced Permissions. We recently launched several permissions enhancements. Instead, now you must use the Short-Lived Token and Refresh Tokens in your applications. The problem is that since September 30th, 2021, Dropbox turn off the Long-Lived Tokens. Recently I was implementing a Dropbox integration with my Java+Spring application using Dropbox API and Java SDK.

Dropbox developer metadata