SWT browser deprecated ?

[FJBDev]

Today, when I try to open the dropbox /authorize webpage with a SWT browser, I get this error :

While it was working all this time, that seems new to me that Dropbox doesn't support the SWT browser anymore?

Can someone share the new Dropbox requirements ?

Thanks

[Greg-DB]

I'm not familiar with "SWT browser", but it is not officially supported by the Dropbox web site. You can find the official system requirements for the Dropbox web site here:

https://help.dropbox.com/installs-integrations/desktop/system-requirements#web

Also, from your screenshot, it appears this may be some sort of web view in your app. Note that you should not be processing the Dropbox OAuth app authorization flow in a web view, per the documentation:

https://www.dropbox.com/developers/documentation/http/documentation#oauth2-authorize

[FJBDev]

Note that you should not be processing the Dropbox OAuth app authorization flow in a web view, per the documentation

Huh, not sure if I understand correctly but when I read the documentation you attached, I read that :

" This isn't an API call—it's the web page that lets the user sign in to Dropbox and authorize your app."

Unless what you are saying "a web view" has a different meaning than a "web page" ??

[Greg-DB]

Yes, the /oauth2/authorize page is a web page on the Dropbox web site. A "web view" is a sort of embedded browser in an app, which can be used to display web pages in the app. We do not officially support displaying the Dropbox /oauth2/authorize web page in a web view. Apps should send the user to this web page in their own system browser, which needs to be one of the officially supported browsers.

[FJBDev]

Oh ok, thanks for this info.

So does that mean I need to ask my users to copy the returned authorization code back in my on-prem software so I can perform a /oauth/token for them ?

By the way, the SWT browser is a browser offered by the SWT framework to display web pages in Java applications for example:

https://download.eclipse.org/rt/rap/doc/2.3/guide/reference/api/org/eclipse/swt/browser/Browser.html

[Greg-DB · Accepted solution]

Thanks for the additional information.

The user only needs to manually copy and paste the authorization code into your app if the app does not provide a redirect URI. If the app provides a redirect URI, the authorization code will be provided via a redirect to that redirect URI after the user authorizes the app. Please refer to the authorization documentation for more information.