ErrorCode=No_Openid_Response

[Kate Andreeshcheva]

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 permanent token to get around this problem, but when I click on the generate button I get a non-permanent token, there is also no button to set the validity time

Do you have any ideas what I'm doing wrong?

[Здравко]

---

@Kate Andreeshcheva wrote:

Hello! I'm trying to integrate Salesforce with Dropbox and got Error in the URL: /AuthorizationError?ErrorCode=No_Openid_Response&ErrorDescription=Bad+response. 

...

---

Hi @Kate Andreeshcheva,

The error you mentioned doesn't come from Dropbox API, so you have to figure out where it comes from and if related somehow to Dropbox, how exactly.

---

@Kate Andreeshcheva wrote:

...

I would also like to get a permanent token to get around this problem, but when I click on the generate button I get a non-permanent token, there is also no button to set the validity time

Do you have any ideas what I'm doing wrong?

---

If you mean access token, no, you cannot get permanent access token. Such option was deprecated long time ago and already dropped for all new tokens (in spite that existing long lived access tokens whenever available/left still work). For long term access you need refresh token (intermediate token that assists access token regeneration and keep it valid). The refresh token doesn't expire automatic and is long lived in this context. Unfortunately, there isn't a way to get such token from application console like it was for long lived access token (not yet at least). For refresh token you will need to perform OAuth flow either flow embedded as algorithm in your application/plugin or externally by hands. If not using some supported SDK, you will need to take care for refreshing process too - mandatory within your application/plugin. If you use some of the supported SDKs, it's done there, so the only thing you'll need to do is proper client object initialization and everything else will stay the same.

Hope this helps.

[Greg-DB]

@Kate 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

[Kate Andreeshcheva]

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.