![]() ![]() ![]() ![]() Yes, most of the examples are simplified. Your assumption is have not seen any examples of this type of use case. (including in env or somewhere else - wherever you Even if I did store the token somewhere my guess is eventually it would want to authenticate again and the script would break.Īgain read my previous post more careful. Yes, you need to store the same as you do it for app id, app secret, etc. To be honest, I have no any idea what you mean here. if I do the refresh token I'd still have to store it but my intention was to just have a simple script and handle the permissions/access by setting something in an env. Probably you haven't read my previous post carefully. basically you can't just have a simple script run on a schedule (not an app that is running) and be able to access the users files without having some sort of interactivity to authenticate? For long term access you need refresh token that doesn't expire automatic and can be reused. ![]() To get refresh token, you need to perform offline access type OAuth flow. The common (border) thing between application authentication and account authentication is OAuth flow. As explained above already, app related authentication cannot replace account related! For long term access you need refresh token that doesn't expire automatic and can be reused. Yes, access token is short lived and works for limited time span (4 hours or so). Otherwise you don't have access to can do what that code does with an access token, but that only works for a few hours thus why I tried to use the app id and secret. To access particular account related thing (like listing some folder in Dropbox account, even when the account is yours) you need to authenticate the account, not application (even when the application is your property). As their name part (app - 'app' key/id and 'app' secret) suppose, it's not account related, but application related. Thanks for the since I'm guessing I am misunderstanding the purpose of the app id/secret. I'll try to get the refresh token thing to work with an access token since I'm guessing I am misunderstanding the purpose of the app id/secret. It sounds like this used to be easy when the access codes were not short lived.Ĭan you tell me if the app id/secret can do this? I have seen other posts by you I think that said the app id/secret does not have access to any particular users DB but somewhere else I read that it should be able to do stuff with the apps folder. I can do what that code does with an access token, but that only works for a few hours thus why I tried to use the app id and secret.Īll of the examples I have seen need to interact with someone via a browser or like that prompt to get a token - but this is just for a script that I want to run on my own files and it will run on a schedule so there won't be anyone around to fill in the prompt. I did look thru lots of example and have not seen anything like what I want to do (node script on schedule). Yes, first time trying to do anything with the dropbox api, and in general I am not the most skilled at this but can usually get the job done. Shouldn't this work? I read in another thread that the app permissions don't allow access to anything but in another place I read I should be able to access the apps folder which makes more sense to me.Īll I want to end up with is a script I will run on a local computer on a schedule to get some shareable links - for my own files which will be in the apps folder. I have the correct id and secret entered when I run it, not ***Įrror listing contents: DropboxResponseError: Response failed with a 409 codeĪt D:\Repos\locket-emailer\node_modules\dropbox\cjs\src\response.js:34:11Īt process.processTicksAndRejections (node:internal/process/task_queues:95:5) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |