-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support the "Code" Authorization flow #64
Comments
Thanks! We'll consider it a feature request. |
I need this functionality as well. But in the meantime I created an "extension" package that does the trick for me. Maybe it could be useful for others too. It can be found here: https://www.npmjs.com/package/dropbox-client-oauth2 |
@greg-db any news on this? |
No, I don't have an update on this. |
@b-dur your module works well for me. Why don't you submit a PR to this one to add the functionality here? 😄 |
The JavaScript SDK now supports the "code" flow as of v3.0.0, via the Make sure you set your app key and secret here, and set |
@greg-db This is great, but what if you don't have a server to redirect to (i.e. running from a CLI script?) EDIT: NVM, figured it out. You can call EDIT 2: Wait, nope, still stuck. Calling |
You'll need application authentication
https://www.dropbox.com/developers/reference/auth-types
…On 29 May 2018 at 22:32, Eliot Lash ***@***.***> wrote:
@greg-db <https://github.com/greg-db> This is great, but what if you
don't have a server to redirect to (i.e. running from a CLI script?)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACpQ2f0pw3qbr6NgfLd60-DW0GJW84unks5t3b6DgaJpZM4Jrlbl>
.
|
@fadookie It looks like |
@xeektech No, I don't have an update on this yet unfortunately. |
Currently, only the
token
authorization flow is working, which is fine for front end frameworks, but using nodejs, it is way more secure to use thecode
authorization flow so that the access token is not exposed to users or browser extensions.I am guessing two things need to be supported here: the clientSecret parameter and a new method for converting a code to an access token.
The text was updated successfully, but these errors were encountered: