We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Re: Best way to authorize more users on my app
Greg-DB ha scritto:I'm not sure I follow. What do you mean by "accessID"?
Sorry I mean accound_id and not accessID
Greg-DB ha scritto:Also, can you clarify what you mean when you say " field state is filled correctly but I don't have the code because it is hidden"?
If in my call I use the field state, the callback does not return the code field but only the state returns to the parameters. How is it possible?ù
Thanks for you help
2 Replies
- Greg-DB
Dropbox Community Moderator
The account_id returned by /oauth2/token is the account ID of the Dropbox account that was signed in and authorized the app, resulting in the authorization code that was used. Dropbox can't attest to the ID of the user in your app that was signed in to your app at the time. You'll need to manage that in your app's session code.
Also, the state and code values are getting returned as expected for me. I just tried this /oauth2/authorize URL (using a redirect URI hosted on Dropbox itself as an example):
Upon authorizing the app, it redirected me to the redirect URL:
That contains the expected state value, as well as an authorization code.
If something isn't working as expected, please share the steps/code to reproduce the issue, and the error or unexpected output.
You can use ?client_id=someid&state={base_encode('user_id')}, just put user_id, or some unique value to the state query param, and Dropbox will return you response as {code: "Some Code", state: 2}, where 2 - is User ID, as an example
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
