Now that DB uses \"short-lived\" tokens, I am having trouble \"automating\" token refresh within an application.

Using the Java code examples, I can get the DB URL where I manually have to log into the DB site, get the new access code, and, again, manually, copy that back to the application (

.ShortLiveTokenAuthorize().authorize(appInfo);

So, my question is ... is there a way to get the new access token programmatically with NO manual steps? So, when the user goes to \"upload\" (in my case), it ... ALWAYS works;

Using OAUTH in other apps I can automated refreshing the token, but I haven't seen an example how to do it with DB.

Thanks in advance!

Now that DB uses \"short-lived\" tokens, I am having trouble \"automating\" token refresh within an application.

Using the Java code examples, I can get the DB URL where I manually have to log into the DB site, get the new access code, and, again, manually, copy that back to the application (

.ShortLiveTokenAuthorize().authorize(appInfo);

So, my question is ... is there a way to get the new access token programmatically with NO manual steps? So, when the user goes to \"upload\" (in my case), it ... ALWAYS works;

Using OAUTH in other apps I can automated refreshing the token, but I haven't seen an example how to do it with DB.

Thanks in advance!

It is not possible to fully automate the OAuth process where the user chooses to authorize the app and the app then receives the resulting access token and optional refresh token. This needs to be done manually by the user at least once.

If your app needs to maintain long-term access without the user manually re-authorizing it repeatedly, the app should request \"offline\" access so that it gets a refresh token. The refresh token doesn't expire and can be stored and used repeatedly to get new short-lived access tokens whenever needed, without the user manually reauthorizing the app.

Here's some example code of processing the authorization flow using the official Dropbox API v2 Java SDK, such as to get a refresh token:

https://github.com/dropbox/dropbox-sdk-java/tree/master/examples/authorize/src/main/java/com/dropbox/core/examples/authorize

For instance, here's a line where it requests \"offline\" access in order to get a refresh token:

https://github.com/dropbox/dropbox-sdk-java/blob/master/examples/authorize/src/main/java/com/dropbox/core/examples/authorize/ScopeAuthorize.java#L39

And here's an example of storing the refresh token:

https://github.com/dropbox/dropbox-sdk-java/blob/master/examples/authorize/src/main/java/com/dropbox/core/examples/authorize/Main.java#L98

As long as you supply the necessary credentials, the SDK will then handle the refresh process for you automatically, e.g.:

https://github.com/dropbox/dropbox-sdk-java/blob/e52fc828c7c753e04c3fa9d47ab6de7e85d000c4/examples/account-info/src/main/java/com/dropbox/core/examples/account_info/Main.java

Thank you!

I used the top Java program you listed to do the manual approach.

If I understood your reply correctly (a show-stopper), I'm disappointed that there's no total programmatic way to get a new token when expired. We can't expect our users to go to the DB website click here and there, get a new access key, and paste it into the client-side application.

Thanks

Yes, that's correct. The SDK client knows how to use the credentials (refresh token, app key, and for the non-PKCE case, app secret) to automatically perform the refresh process whenever needed, so that calls continue to work.