We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
What if I want the User to login each time
I don't want to keep my own user membership db and login logic for my web app. My web app is going to be only for Dropbox and I want to rely on Dropbox Login only. Otherwise, saving the access token ...
This is sort of already possible. If you send the user through the app authorization flow again, they may (e.g., as long as your app's redirect URI uses https://) be automatically redirected, without having to click "Allow", if they've already authorized the app. You can find a note about this under "force_reapprove" in the documentation:
https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize
Note that this still will return a new access token to your app though.
That's exactly what I want. That means, I can just save a flag in the cookie that says it was approved once. And use it to switch on that option. Switch it off only if the user wants to switch the dropbox accounts by some other action.
>>Note that this still will return a new access token to your app though.
That's OK. Will it create a problem for Dropbox system itself to have too many access tokens generated? Or does it automatically recycle by invalidating the old one?
Thanks,
Sanjay
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThere isn't a limit to the number of access tokens that can be created for an app-user pair, and I'm not aware of any issues arising from creating many. Dropbox won't automatically recycle/invalidate them.
Finally, I was able to test it with https and it works perfectly. In fact, if I follow this approach, it works automatically, asking for login only once and then navigating automatically. This is great.
Thanks,
Sanjay
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
