Dropbox OAuth API v2 not working after migration - oauth

Here's the problem. I was using OAuth 1.0 to authorize and upload files to Dropbox with my app registered.
I Followed the migration guide but facing some issues in Auth.
Here are the URLs of HTTP APIs used in V1:
/1/oauth/request_token
/1/oauth/authorize
/1/oauth/access_token
for authentication.
Can anyone help me with the corresponding URLs supporting DB API v2 please? (Along with the parameters...)

Dropbox API v1 supports both OAuth 1 and OAuth 2. Dropbox API v2 supports OAuth 2 only.
The documentation for the OAuth 2 endpoints for use with Dropbox API v2 can be found here:
https://www.dropbox.com/developers/documentation/http/documentation#authorization
There's also an OAuth guide which may be helpful here:
https://www.dropbox.com/developers/reference/oauth-guide

Related

Zend Framework 2 and OAuth how to create provider?

I'm looking for a way to secure my own api with OAuth, but all I find is how to create client that connects to Twitter or Facebook. In the ZF2 docs site there is only example how to use ZendOAuth to connect to Twitter service. Is there any tutorial/documentation or anything ?
Which version about Oauth you are looking for ?
Just add one of these modules to create an Oauth provider. Take care! you have to know how oauth works, to integrate into your application.
For oauth 1.0a
https://github.com/bgallagher/BgOauthProvider
For oauth 2.0
https://github.com/php-loep/oauth2-server
see https://stackoverflow.com/a/23302428/389976
Essentially check out Apigility http://www.apigility.org/

Google Apps Script "Upgraded Authorisation Experience" and OAuth

I have been playing with the new Admin SDK in conjunction with the "upgraded authorisation experience" and wondered if someone has and experience/examples on how to use it. From what I have read, if you upgrade the authorisation experience you shouldn't need to use OAuth 2.0 and get a client ID and secret from the API console.
When you upgrade the authorisation, the API console entry is automatically created so you just have to turn on Admin SDK. Your app should then run simply using your own admin credentials.
Have I misunderstood this and if so, what is the benefit of the new authorisation experience?
I can use the Admin SDK just fine if I create a client ID and secret in the API console but this is using OAuth 2.0 then.
If someone has an example of how to use the admin sdk with OAuth 1.0 i could have a look at it would be much appreciated.
You will still need get your tokens and API key...
Take from the Directory API documentation:
If your application has certain unusual authorization requirements, such as logging in at the same time as requesting data access (hybrid) or domain-wide delegation of authority (2LO), then you cannot currently use OAuth 2.0 tokens. In such cases, you must instead use OAuth 1.0 tokens and an API key. You can find your application's API key in the Google APIs Console, in the Simple API Access section of the API Access pane.
If you are looking for an oAuth2 example with GAS, Arun has a nice example he posted on GitHub, see the SO posting: How to authorize with oauth 2.0 from appscript to Google APIs?
Sorry, I don't have any oAuth1 example to interface with the new APIs.

Google Translator API OAuth Authentication

Iam developing a multi lingual application and planning to use google translator API. I was wondering if Google Translate API supports OAuth authentication or not, document is available for using key but no information is available regarding OAuth authentication.
Thanks

Does google Drive api support 2 legged oauth?

Now, we have an application with Google Docs Api and 2 legged oauth. However,we want to migrate to Google Drive Api which uses Oauth 2.0.
Can we use 2 legged oauth with Google Drive Api?
Is there any example?
You should use Service Accounts: https://developers.google.com/accounts/docs/OAuth2ServiceAccount
I just started looking into this and if I have any luck I will provide more info.
However, if you are using 2 legged oauth so you can work with google apps domain-wide then there is a published guide. I believe this is what the other answer was talking about.
Blog post explaining domain wide delegation: http://googleappsdeveloper.blogspot.com.es/2012/11/domain-wide-delegation-of-authority-and.html
Guide for the drive API: https://developers.google.com/drive/delegation

Single sign on for google api's using Scribe?

Is there anyway to retrieve the Google Oauth refresh_token using Scribe?
I am building an app that requires several scopes mixed between java Gdata and Google api java client libraries -- and I am looking for a Single Sign On (SSO) when a user of my app signs in. However because of the state of current Google Apps API's requiring Oauth 1 or Oauth 2 depending on which library / scope you need, I'm a bit stuck.
Oauth 1 (java gdata e.g. analytics data export scope) - requires the
access_token secret
Oauth 2 (google api java client e.g. analytics calendar scope) -
require a refresh token, which is not avail currently in a Scribe OAuth 1 call
Any tips / advice? Anyone managing this with a single sign on?
Sorry scribe does not support (at the time of this writing) Google's OAuth 2.0 Apis.
It shouldn't be too hard to implement using FacebookApi as a guide. Cheers!
Scribe has added support for Google OAuth API. I used scribe 1.2.2 and it worked just fine for me.

Resources