You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
ErrorCode=No_Openid_Response
Hello! I'm trying to integrate Salesforce with Dropbox and got Error in the URL: /AuthorizationError?ErrorCode=No_Openid_Response&ErrorDescription=Bad+response. I would also like to get a perma...
Greg-DB
Dropbox Staff
Dropbox StaffKate Andreeshcheva Здравко is correct. Dropbox is no longer offering the option for creating new long-lived access tokens. Dropbox is now issuing short-lived access tokens (and optional refresh tokens) instead of long-lived access tokens. You can find more information on this migration here.
Apps can still get long-term access by requesting "offline" access though, in which case the app receives a "refresh token" that can be used to retrieve new short-lived access tokens as needed, without further manual user intervention. Refresh tokens do not expire automatically and can be used repeatedly. You can find more information in the OAuth Guide and authorization documentation. There's a basic outline of processing this flow in this blog post which may serve as a useful example.
And as Здравко said, the error you shared does not appear to be coming from the Dropbox API itself. If you still need help with the Dropbox API, please share:
- the name and version number of the platform and SDK/library you are using, if any
- the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
- the full text of any error or unexpected output from the Dropbox API itself
I use Salesforce Auth Providers and Named Credentials for authorization.
https://help.salesforce.com/s/articleView?id=sf.safety_cloud_auth_provider_creds.htm&type=5
After creating the provider, it generates a connected callback for me, which I place in my dropbox app.
Then I try to authorize, after entering my username and password, I am redirected to my connected callback with errors in the parameters: my_domain/_nc_external/identity/sso/ui/AuthorizationError?ErrorCode=No_Openid_Response&ErrorDescription=Bad+response
I found the same problem on the SF forum, and it seems that the problem is that Dropbox sends user information as jwt, but salesforce expects json. So far this is the only explanation for what is happening
https://salesforce.stackexchange.com/questions/202308/openid-connect-bad-response
Is it possible to customize the return type of response from Dropbox?
Kate Andreeshcheva, You're not performing the OAuth flow to Dropbox yourself as you have described. If you have some suspicious behavior from your platform ask the platform supplier; it's not a Dropbox product!
Kate Andreeshcheva wrote:...
I found the same problem on the SF forum, and it seems that the problem is that Dropbox sends user information as jwt, but salesforce expects json. ...
😁 For sure it's not the same and doesn't explain anything. The access point /oauth2/token gives back JSON, not something else 😉. If your platform does something else... 🤷 it's another story.
Kate Andreeshcheva wrote:...
Is it possible to customize the return type of response from Dropbox?No, JSON is always returning.
Hope this gives direction.
- Greg-DB
Kate Andreeshcheva To confirm what Здравко said that's not made by Dropbox, and so Dropbox can't offer support for that. If you need help on the Salesforce side of things, you'll need to contact Salesforce.
As for the Dropbox side, as Здравко linked to you can find the documentation for the Dropbox /oauth2/token endpoint here, and you can also find more information on our OpenID Connect functionality here.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
