We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
Localhost
As reported by the documentation I used http: // localhost as a redirect uri. Since my system did not allow me to access this page, I installed microsoft IIS: now http: // localhost is accessible and...
The redirect URI you use (if any) is up to you as the developer. It is intended to be a URI you control, but you can choose whatever is appropriate and functional for your scenario.
It's not clear how you're accessing the authorization code on the redirect URI if you don't control the redirect URI though, since that URI is on a domain/server you presumably don't have access to. Note that the OAuth app authorization flow should not be processed in an embedded browser or web view, per the documentation; it should only be processed in the user's system browser.
As I said my app works perfectly if I use the Microsoft OneDrive uri redirect. I wonder if this is a valid solution or if instead it is better to experiment with a different redirect uri, more linked to the DropBox world. Thanks for the reply.
Greg-DB
Dropbox Staff
Dropbox StaffThe redirect URI you use (if any) is up to you as the developer. It is intended to be a URI you control, but you can choose whatever is appropriate and functional for your scenario.
It's not clear how you're accessing the authorization code on the redirect URI if you don't control the redirect URI though, since that URI is on a domain/server you presumably don't have access to. Note that the OAuth app authorization flow should not be processed in an embedded browser or web view, per the documentation; it should only be processed in the user's system browser.
