You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Java SDK issues with short lived token
Hi there, I need some help to migrate to the short lived token.
Normally I check if I have the token, then call or execute the other doprobx APIs (e.g. file upload):
Auth.startOAuth2Authentic...
Hi, I am also looking to migrate to short-lived token. Thank-you for posting the usage examples.
One question I have is, if I update my code, using startOAuth2PKCE method, will that affect my Access Token Expiration setting in appConsole (currently set to No Expiration) for other apps accessing Dropbox? Basically I just want to make sure that if I start testing with startOAuth2PKCE method, that it won't affect my current apps and users in production, as, in addition to an Android app, I have an iOS app and a Java Desktop app as well (which I plan to migrate later).
Greg-DB
Dropbox Staff
Dropbox Staffvewert No, just using the startOAuth2PKCE method will not change the "Access token expiration" setting in the App Console for any of your apps.
Thanks for your quick response, so using startOAuth2PKCE method with give a Short Term Token, even if my app console is set to No Expiration?
- Greg-DB
vewert Yes, that's correct. The the "Access token expiration" setting in the App Console is essentially a setting that controls the default behavior when token_access_type is not specifically set by the app during the authorization flow. The startOAuth2PKCE does set that though, so it will still return a short-lived access token/refresh token.
Ah, that clarifies things. Thank-you for your help, it is very appreciated.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
