We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
.NET API - Authorization issue
Hi all, We have an app that relies on the business API. It creates groups, members, team folders, etc. As a team administrator, I can run it and it's working properly. My problem is that the targete...
Thank you for this information. But it's really hard to find out how to implement the scopelist parameter with the .NET SDK. I was unable to find working examples on the internet. Anyway, I decided to change the approach. We will use a generic admin user in conjonction with a refresh token, so that the users don't have to approve the app with their own rights.
Best regards,
Ghislain
Just to be more explicit on the difficulty I met with your suggestion: when some team scopes are being left checked in the application permission page, I keep on receiving error messages telling me I must be team admin to authorize the app. When I uncheck all the team items and provide a scope list, I get an error 400 as follows:
-------------------------------------------------------------------------
It seems the app you were using submitted a bad request. If you would like to report this error to the app's developer, include the information below.
More details for developers
No scope requested can be granted for this app.
-------------------------------------------------------------------------
When I search for information about this error message, I find that I need to declare all the scopes in the settings. It's a vicious circle!
- Greg-DB
Dropbox Staff
Ghislain Sommervogel Thanks for following up. I'm sorry to hear about the difficulty you've had configuring this. So that we can take a closer look at this error and offer some help, can you share the full URL of the page showing this error?
Hi Greg, yes, sure:
But don't spend too much time on this, because - as I said - we switched to another approach. I ran into a new problem with the refreshtoken setup, but I will expose it in a new thread.
Have a nice evening!
Ghislain
- Greg-DB
Thanks! Yes, to confirm, this URL is requesting only the "groups.write" scope, via the "scope=groups.write" parameter, but the app for that client_id doesn't currently have "groups.write" enabled, so this request can't be serviced, and accordingly this error is returned. To avoid this error, you would need to either not request this scope in the URL, or enable this scope on that app (which may involve enabling other scopes it depends on).
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
