This process will result in more re-authorization flows than before, but will have minimal impact on the end user experience. If the user has already authorized the app (and is logged into Dropbox), then a new short-lived is issued and they’re redirected to your app without any input from the user. When a user tries to access your app with an invalid token, redirect them to the authorization URL you use in your OAuth flow. You can find more information about setting up the right authorization flow for your app in the OAuth Guide. We recommend starting with this approach during migration, then, once you’re confident in your app’s behavior, update the default access token type to short-lived in the App Console. You can programmatically issue short-lived tokens with a small adjustment to your code-including token_access_type=online in your authorization URL. Testing short-lived access tokens with token_access_typeīefore migrating your app to short-lived tokens, we recommend testing them in your app. If your app doesn’t properly handle 401 errors or needs to interact with the Dropbox API without user input (“offline” access), then it may require code changes. If your app handles errors with 401 status correctly and only calls the Dropbox API when users are interacting with it, then it shouldn’t need any code changes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |