Child Item

Authorization and unattended batch process

Is it possible to return an access token without human intervention during the authorization process? I am writing a batch process to be run on a server that connects to a dropbox app with AppKey:AppSecret and checks for newly created files and copy them to a server and record the file details. However, it seems that the decision to authorise and send an access key cannot be automated and requires the owner to press something. Am I being particularly stupid and missing something obvious?

Thanks in advance

Glenn

Find more posts tagged with

API

Abuse

Accepted answers

GlennAlligator

Yes got it working now. I thought the access token would only have a very short persistence and that it needed to be rebuilt for every session. As the access token never expires that will work great.

Thanks

All comments

TaylorKrusen

Hi Glenn,

You can't return an access token without some element of human approval. Almost all OAuth Flow implementations require that a user gives consent to share their data with your application.

GlennAlligator

Thanks for your reply Taylor.

Yes, this is how it looks so I'll have to find another way. Many Implementations of the Implicit mode include X509 certificates which I think gives you better security than just relying on Key/Secret pair. I know that Implicit mode is frowned upon generally but so many processes are run as back-end server batches which by the very nature are unattended and run at 2 o'clock in the morning. I don't mind jumping thru as many software hoops as might be required but to not have a way of setting up unattended server batches is a major failing in dropbox.

TaylorKrusen

Hi Glenn,

Is there a specific reason that your application needs to reconnect with the Dropbox app every time the script runs?

Generally speaking, most integrations would use a stored Access Token in order to run their script and automate the collection of data. OAuth Flows are really only necessary when you need users to explicitly authorize your app to use their data.

GlennAlligator

Yes got it working now. I thought the access token would only have a very short persistence and that it needed to be rebuilt for every session. As the access token never expires that will work great.

Thanks

TaylorKrusen

Excellent! Happy to hear that.

Please feel free to post again if another question come up in the future!