We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
The design of Dropbox's AUTH CODE page.
I'm creating an Android app that accesses to Dropbox API.
To access Dropbox, users have to get access token using OAuth 2.0.
In this process, before getting the access token, users have to copy...
Thanks for the additional information! I'll send this along as a request to optimize this page, but I can't make any promises.
We do still highly recommend trying a redirect URI though. The /oauth2/authorize, which is still used even if you use a redirect URI, does also allow the user to switch Dropbox accounts. (In fact, switching accounts after hitting "Allow" would be too late to change what account is linked to the app anyway.)
It sounds like you may not want to use a redirect URI because it sometimes doesn't give the user a chance to switch though, since it may automatically redirect the user if they've already authorized the app. If that's the case, you should set force_reapprove=true to disable that behavior.
Thank you for the advice.
I'd already tried the redirect_uri, but I didnt use it finally,
because it is impossible or very difficult to install account selector in the redirect page.
Compared with the redirect page, Dropbox's ready-made page has built-in account selector.
It is beneficial not only for developers but also for Dropbox's users who would like to change using account case by case.
Regarding text selection, I don't think it is 100% due to each Android version.
I think that the auth code displayed in the Dropbox's ready-made page is too small compared with the human's finger.
It is so difficult to point the target. I think the size of text should be widened boldly.
I used very big fonts using CSS in the redirect page I mentioned above. It was so easy to select auth code.
I think it relatively easy to re-design Dropbox's ready-made page.
Only a few SCC are required, aren't they?
I hope Dropbox's customer-friendly API.
best regards
Greg-DB
Dropbox Staff
Dropbox StaffThanks for the additional information! I'll send this along as a request to optimize this page, but I can't make any promises.
We do still highly recommend trying a redirect URI though. The /oauth2/authorize, which is still used even if you use a redirect URI, does also allow the user to switch Dropbox accounts. (In fact, switching accounts after hitting "Allow" would be too late to change what account is linked to the app anyway.)
It sounds like you may not want to use a redirect URI because it sometimes doesn't give the user a chance to switch though, since it may automatically redirect the user if they've already authorized the app. If that's the case, you should set force_reapprove=true to disable that behavior.
Hello Greg, Thank you for the kind advice.
"force_reapprove=true" is truly nice!
I'll try redirect-page with it readily.I really appreciate your support. <(_ _)> :stuck_out_tongue_winking_eye:
Hi Greg,
Finally I used "force_reauthentication=true" to force users to choice their accounts before they are lead to the redirect-page.
Anyway, thank you for your advice. :stuck_out_tongue_winking_eye:
Please anybody tell me how to set the force_reauthentication as true in authorization url.
DbxWebAuth.Request webAuthRequest = DbxWebAuth.newRequestBuilder().withForceReapprove(true).withRedirectUri(finalUrl, getSessionStore(httpServletRequest)).build();
in the above code, there is method for setting force_reapprove as true but no method for force_reauthentication as true.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
