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
2 console application 1 account -
if i have a user the authenticate in one application get access refresh tokens.
then authenticate in another application is the old token will stop working
or every authentication can exist no matter what.
i am asking this because my company toll doing a migration many for each user ,
if during the migration the user will authenticate again in order to run another migration does the old token will expire and i need to use the new token also for the old migration ?
is my explanation clear ?
Refresh tokens do not expire automatically, but they can be revoked by the app or user on demand. That means by default you do not need to get a new refresh token for an account that is already connected (unless it is explicitly revoked by the app or user).
Short-lived access tokens do expire after four hours. A refresh token is used to perform the "refresh", which is a way to get a new short-lived access token. The Dropbox .NET SDK will do that for your automatically so you don't need to implement that yourself.
- Greg-DB
Dropbox Staff
Authorizing a new application does not affect existing app authorizations. If you get a refresh token for a particular app on an account, existing refresh tokens for other apps on that same account will not be affected. Accounts can have multiple apps connected at the same time.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
