How to use node-red-node-dropbox without a browser?

[georgevbsantiago]

Hello,

How can I use 'node-red-node-dropbox' without a browser on localhost?
I use a NodeRed instance in which I do not have access to the browser to perform steps to obtain the 'Access Code' and the 'Refresh Token'.

I read several topics about 'node-red-node-dropbox', but the examples are using the browser to obtain the 'Access Code' and the 'Refresh Token'. But how do I get the 'Access Code' and 'Refresh Token' without access to the browser?

[jbudd]

Hi @georgevbsantiago, welcome to the forum.

Is there any reason to believe that you must obtain a token on the same machine as runs Node-red?
Since you must be able access your Node-red instance with a browser from somewhere, does that not let you set up the token?

Have you tried obtaining one using a completely seperate PC and browser and copying the values manually into Node-red?

[georgevbsantiago]

Hello, Thanks for the posts

I read some posts about node-red-node-dropbox (mentioned below) and understood that access via oauth2 token would have to be done on the same machine that generates it.
Ex: If NodeRed (node-red-node-dropbox) is on VPS 'A', the oauth2 token would have to be generated in the browser of VPS 'A' instance to work.

Refresh tokens in node-red-node-dropbox (Now published as v2.0.0)

To get it working on my raspi, I had to open the browser in the raspi because only local is allowed to get my Refresh Token. Since everything was set up locally, I was able to back up again from mac safari.

@BartButenaers

I wasn't aware that only local was allowed. Will need to to find some time in the weekend to try this myself. Thanks for testing this!!!!

@BartButenaers

As @Frida already experienced, the hostname in the dropbox redirect_uri must match the hostname used to access the flow editor.

1. If you want to use localhost in your redirect_uri, then you need to use the browser that is installed on that host. Because the browser installed e.g. on a raspberry, can access local resources on that same raspberry via localhost.
2. But normally if you access your flow editor via https://my_rpi_name:1880/some_path, then the redirect uri should be https://my_rpi_name:1880/dropbox /authenticate

Am I correct that there is only a problem for Node-RED systems that fulfill the following 2 conditions:

1. The system is not accessible via localhost, because there is no browser installed on that host.
2. And SSL is not enabled (via the Node-RED settings.js file.

Because dropbox requires https, unless you use localhost.

Not sure if there is anything I could do about that, to be honest...

I understood that if the user manipulated NodeRed (node-red-node-dropbox) on VPS 'A', but tried to create the token on their personal computer (notebook, PC...), it would not work.

If it is possible to manipulate NodeRed (node-red-node-dropbox) on VPS 'A', and create the token on my notebook to later insert it into node-red-node-dropbox) on VPS 'A', then that's great!

Question: Is there no way to avoid manually creating the oauth2 token by opening Dropbox through the browser?
I upload it to Dropbox via script, using the access token (old way), using the SDK-Dropbox JavaScript and just providing 'token' and 'account_id', without prior access via the browser.

Thank you for your attention

[jbudd]

OK, I read the post you linked to but didn't understand it all (and not just the Portuguese!).
Maybe someone else more knowledgable can assist you.

[georgevbsantiago]

I managed to generate the refresh token through my browser (laptop) and inserted it into node-red-node-dropbox. Thanks.