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
Using API in Salesforce with Named and External Credentials and OAuth2 upload OK but call to file sh
I have setup OAuth2 in Salesforce along with Named Credentials and External Credentials. I am calling the File Upload API in the code..that works fine with all the above. I setup a second Named Cred...
DB-Des
Dropbox Engineer
Dropbox EngineerHi bossgolfer,
A 'missing_scope' error indicates that while the app may be permitted to use that scope, the particular access token you're using to make the API call does not have that scope granted. Also, be aware that just adding a scope to your app via the App Console does not retroactively grant that scope to existing access tokens or refresh tokens.
That being the case, to make any API calls that require that scope, you will need to re-authorize the app to get a new access token (and refresh token, if being used) with that scope.
Alternatively, apps can request different scopes, per authorization, using the scope parameter in the Authorization URL. Doing this would grant the scope(s) set in the URL to the resulting token only — it would not update the app's pre-set permissions, nor would it affect any other tokens.
Additionally, we would recommend you confirm that the client_id of the app, with the sharing.write permission enabled, is the one being used in the Authorization URL.
You can refer to the OAuth Guide and authorization documentation for more information.
To answer your additional questions:
1. The access token generated in the app is not permanent, it does expire.
2. Could you expand on what blocks you may be encountering as far as wanting to "chunk load larger files"?
3. Could you also further explain what you mean by "getting a second token on a second HTTP callout is a problem when calling the different API"?
To answer your additional questions:
1. The access token generated in the app is not permanent, it does expire.
2. Could you expand on what blocks you may be encountering as far as wanting to "chunk load larger files"?
>>> I actually got that working OK.
3. Could you also further explain what you mean by "getting a second token on a second HTTP callout is a problem when calling the different API"?
Its just not clear to me what was causing the missing scope on the sharing call after the initial call to file upload.
So do you recommend going back the the Oauth access vs the token.
- DB-Des
bossgolfer, It is recommended to get an access token via an OAuth flow, yes.
Keep in mind that access tokens, whether obtained from the app within the App Console or via OAuth flow, will eventually expire. The expiration time can be confirmed in the property
expires_in, which is found in the response object returned from the /oauth2/token endpoint.I hope this information provides more clarity!
Thanks. I went the route of Auth Provider plus Named and External Credentials in Salesforce and all is working well.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
