I would very much like to enable users of my app to backup some of app data on their own Dropbox. I would like to direct users to login to their Dropbox account with their email and password and then the app would generate and store a file there without users having do anything on their own.
Is this possible?
I wouldn't want users to have to go to Dropbox App Console and then Create App and then fill in all the options and then copy the access token and paste in my app manually. That would repel a lot them.
I haven't seen anything in the docs suggesting that programmatic access to an account without an app created in the Console and generated access token is possible? Did I miss something?
Yes, this is possible. You as the developer would register the app once, and implement the Dropbox OAuth app authorization flow in your app to allow your end-users to then connect your app to their accounts.
You may want to check out the following guides:
https://www.dropbox.com/developers/reference/getting-started
https://developers.dropbox.com/oauth-guide
https://developers.dropbox.com/dbx-file-access-guide
Related
I'm trying to change my Dropbox application permission from 'App folder' to 'Full Dropbox'. By application I mean 'My apps':
I'm doing this to access all the functions provided by Dropbox API, otherwise an error is shown, for example:
Error in call to API function "sharing/get_folder_metadata": Your API app is an "App Folder" app. It is not allowed to access this API function.
Anyway, I've read that the only way to change the permission to an app is by creating a new one. Therefore, what I did was, created a new app with permission type 'Full dropbox' but for some reason it didn't even show up under 'Dropbox > Apps' directory.
According to developers guide if app has permission App folder then it is moved under Apps folder automatically. I tried also that but the folder didn't appear there for some reason. So, why the first application is showing..
Can there be only one active app, like, should I download all the data from first one, delete it and then create new app with Full permissions?
It's not possible to switch the permission on an existing Dropbox API app.
If you want to change the permission used for an app that hasn't been released to users, you can do so by deleting the current API app registration and registering another with the desired permission. Deleting an API app in development mode frees up the name so you can register it again. Once you do, just be sure to update your app accordingly to use the new app key and secret. Access tokens for the deleted app will also no longer work.
If your app has already been released to users, we do not recommend disabling your API app, as it would break the integration for existing users. Instead, we recommend you register another API app for the other permission and add that as an option in your app.
You can register a new API app here:
https://www.dropbox.com/developers/apps/create
There isn't a limit on the number of API apps that can be owned by or linked to a particular account.
Your second App Console screenshot shows that you do own two API apps: one with the "app folder" permission, and one with the "full Dropbox" permission.
Note that only apps with the "app folder" permission get a special "app folder" automatically created under "/Apps". Apps the with "full Dropbox" permission do not, and instead can access any path in the account.
I want to upload files to google drive. I'm using C# and have referred following links to get started
https://developers.google.com/drive/v3/web/quickstart/dotnet
https://developers.google.com/drive/v3/web/manage-uploads
I'm able to upload the file successfully to google drive but my main concern is I don't want to display any sort of UI/human interaction. It should be able to automatically upload the file.
Using OAuth2.0 there is a need that we have to manage and generate access/refresh token. I have no idea how these should be managed.
Isn't there any other way where the user can have access to google drive programmatically just by sharing his/her Gmail account username/password to achieve this?
Isn't there any other way where the user can have access to google drive programmatically just by sharing his/her Gmail account username/password to achieve this?
No there is not
The user needs to authorise your app one time. After that, you can save Refresh Token and use that for future unattended use.
I have a Dropbox account.
I would like to use it, so that an android app can upload photos to my Dropbox account, without the user of the app having to know my credentials to log in.
Is that possible ?
Is there a programmatic way, that I can get my app to do this, without the user of the app having to know my dropbox password ?
EDIT: I don't understand why this is down voted. If there are multiple posts asking how to do this, by different users, and it is with regard to finding a programmatic why to log in, then it is relevant and shouldn't be down voted.
Refer to this thread on dropbox forums which says that they did not include the file requests feature in their apis so its not possible through apis.
Since the native api does not support this feature you can redirect your user from your app to dropbox app to create file requests.
I've built a simple app that consumes the Google Analytics API.
I have authorized access through OAuth 2, but have only been using my account to save access and refresh tokens.
If I want to let others use the app, will I need to save an access token for each user?
For web app, you just need one, and put the tracking code in every page of your app.
I'm not sure about native app.
I have an app with a dropbox link capability. There is a button called link. Then a safari page is opened with dropbox, and you can link the app to your account. But since I want all the users to log in with my account, I didn't want to dysplay my email and passward on the app, but by preesing link, automatically the app is linked with my account, withought showing the passward, amd withought opening the dropbox link in safari. How can I do this?
Very bad idea. Users should use their own Dropbox account, otherwise you would possibly violate Dropbox's terms of service (you're not allowed to share your credentials) and, perhaps more importantly, any user would be able to delete or corrupt all other users' data.
The only way you could make your own Dropbox account accessible in the app, other than including your email address and password, would be to include an authorized OAuth token which could easily be extracted and abused by anyone who downloads your app.