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

Ditza's avatar
Ditza
Explorer | Level 3
4 years ago

Use short live access token - with SwiftyDropbox

Hi,

I just move my app to use a short live access token.

There are some points I am not sure about

1. If I am using the SwiftyDropbox SDK, It handles the refresh token process. I just need to use this function

authorizeFromControllerV2

instead of this 

authorizeFromController

2. Do I need to set the token to a short one in the app console? or does this "authorizeFromControllerV2" get only short tokens?
3. The access token spouse to be of 4 hours, but the "tokenExpirationTimestamp" is set to "1630253071.708452".
In which units is the timestamp?

  • 1. Yes, using the authorizeFromControllerV2 method in the SwiftyDropbox SDK will handle this automatically for you. It will make the SDK request, store, and use a refresh token for the client automatically.

    2. You are not required to change the "Access token expiration" setting for the app on the app's page on the App Console. That only controls the default token type that gets returned for the app when the app does not specifically request a particular type. When using the authorizeFromControllerV2 method in the SDK, it specifically requests short-lived access tokens and a refresh token, so that setting won't affect it. (It would affect any clients for that app that are still using authorizeFromController.)

    3. The tokenExpirationTimestamp value is a Unix timestamp, that is, the number of seconds after epoch, identifying the time when the short-lived access token expires (which would be four hours after it was issued).

  • Greg-DB's avatar
    Greg-DB
    Icon for Dropbox Staff rankDropbox Staff

    1. Yes, using the authorizeFromControllerV2 method in the SwiftyDropbox SDK will handle this automatically for you. It will make the SDK request, store, and use a refresh token for the client automatically.

    2. You are not required to change the "Access token expiration" setting for the app on the app's page on the App Console. That only controls the default token type that gets returned for the app when the app does not specifically request a particular type. When using the authorizeFromControllerV2 method in the SDK, it specifically requests short-lived access tokens and a refresh token, so that setting won't affect it. (It would affect any clients for that app that are still using authorizeFromController.)

    3. The tokenExpirationTimestamp value is a Unix timestamp, that is, the number of seconds after epoch, identifying the time when the short-lived access token expires (which would be four hours after it was issued).

    • FrustratedUser3's avatar
      FrustratedUser3
      Collaborator | Level 8

      It's not clear from your response if the sdk stores the token in CoreData, memory, or somewhere else. The documentation does not mention the storage location either. Please explain how the token storage works and how the app gains access to the token if the app has been killed, removed, reinstalled, etc. These details should be explained in the documentation.

About Dropbox API Support & Feedback

Node avatar for Dropbox API Support & Feedback

Find help with the Dropbox API from other developers.

5,895 PostsLatest Activity: 2 minutes ago
328 Following

If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.

For more info on available support options for your Dropbox plan, see this article.

If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!