API secret in dropbox.oauth.DropboxOAuth2FlowNoRedirect and redistribution

[salven]

Hi,

 I am writing a simple app in the form of a python script which follows the OAuth2 procedure for the user to link and use their own account. Now, the DropboxOAuth2FlowNoRedirect() method requires both the app key *and* secret to be passed and I can't seem to reconciliate this with replies to similar questions, where it was specified that only the key is really needed. How would I go to redistribute the app without embedding (or revealing) the app key?

[Greg-DB · Accepted solution]

The Dropbox OAuth 2 app authorization implementation supports two different flows:
- the "code" flow: this flow requires both the app key and secret
- the "token" flow: this flow only requires the app key

The `DropboxOAuth2FlowNoRedirect` class in the Dropbox Python SDK uses the "code" flow, so it requires the app key and secret.

The Python SDK doesn't implement the "token" flow unfortunately, but I'll pass this along as a feature request. 

That being the case, to distribute a client-side Python app without including the app secret, you'd need to implement the token flow yourself, either by modifying the SDK or without using the SDK at all. Note that the token flow requires a redirect URI though, so you'd need to use a local redirect URI.

[salven]

Thank you, Greg, that helps a lot.

[Manotai M.]

การทำงานversionเก่ามีผลต่อการใช้งานในDropboxของฉัน

[Greg-DB]

@Manotai M. If you're having trouble with Dropbox itself, you can contact support here:

https://www.dropbox.com/support

[This thread is now closed. If you have a similar or new question, you can ask here]